| View previous topic :: View next topic |
| Author |
Message |
BruceG
n00b
Joined: 21 Jul 2003
Posts: 27
Location: Saskatoon, SK, Canada
|
 Posted: Mon Jul 21, 2003 9:01 pm Post subject: ProPolice and glibc 2.3.2 |
 |
|
Greetings.
I am trying to emerge glibc-2.3.2-r1 with ProPolice (-fstack-protector) enabled. According to http://www.gentoo.org/proj/en/hardened/propolice.xml the problems with glibc and sandbox are no longer present in glibc 2.3.2, however when I try to do the ebuild, I see the following error message:
* You have both -fstack-protector and sandbox enabled
* glibc will not compile correctly with both of these enabled
* Please disable sandbox by calling emerge with FEATURES="-sandbox"
Should I disable the error message in the ebuild, or are there in fact still problems with -fstack-protector and glibc/sandbox?
Thanks. |
|
| Back to top |
|
 |
watersb
Apprentice
Joined: 04 Sep 2002
Posts: 297
Location: take a left turn in Tesuque
|
| Posted: Thu Jul 31, 2003 5:04 am Post subject: Re: ProPolice and glibc 2.3.2 |
|
|
| BruceG wrote: |
Should I disable the error message in the ebuild, or are there in fact still problems with -fstack-protector and glibc/sandbox?
|
Try it and see what happens! 
The worst that could happen is that you destroy your system via a broken glibc. That is *very* unlikely in this case, I think. Much more likely is that the ebuild will not be able to finish.
But in any case, before you EVER perform a glibc build, I would make a backup of your system and make certain that you could restore the system if necessary.
Good luck! |
|
| Back to top |
|
|
frogger
n00b
Joined: 05 Dec 2002
Posts: 35
|
| Posted: Thu Jul 31, 2003 8:21 pm Post subject: |
|
|
This warning should have been removed with the glibc 2.3.2 ebuilds, but somehow has managed to stick around. ProPolice/glibc/sandbox all work together as of glibc 2.3.2.
I just removed the warning from the 2.3.2 ebuilds and committed it to cvs.
Go ahead and give it a try  |
|
| Back to top |
|
|
kahcepb
n00b
Joined: 08 Apr 2003
Posts: 34
|
| Posted: Wed Aug 06, 2003 3:44 pm Post subject: |
|
|
2frogger: tried...no luck
| Code: |
.......blahblah..............
u/elf-init.o -MD -MP -MF /var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2/buildhere/csu/elf-init.o.dt
In file included from ../sysdeps/unix/sysv/linux/sys/sysctl.h:29,
from ../include/sys/sysctl.h:2,
from ../sysdeps/unix/sysv/linux/dl-osinfo.h:22,
from ../sysdeps/generic/libc-start.c:33:
/lib/modules/2.6.0-test2-mm4/build/include/linux/sysctl.h:33: error: parse error before '*' token
/lib/modules/2.6.0-test2-mm4/build/include/linux/sysctl.h:35: error: parse error before '*' token
/lib/modules/2.6.0-test2-mm4/build/include/linux/sysctl.h:36: error: parse error before '*' token
/lib/modules/2.6.0-test2-mm4/build/include/linux/sysctl.h:37: error: parse error before '*' token
/lib/modules/2.6.0-test2-mm4/build/include/linux/sysctl.h:40: error: parse error before '}' token
distcc[6792] ERROR: compile on 192.168.1.140 failed with exit code 1
make[2]: *** [/var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2/buildhere/csu/libc-start.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2/csu'
make[1]: *** [csu/subdir_lib] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r3/work/glibc-2.3.2'
make: *** [all] Error 2
!!! ERROR: sys-libs/glibc-2.3.2-r3 failed.
!!! Function src_compile, Line 434, Exitcode 2
!!! (no error message)
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-glibc-2.3.2-r3-28188.log"
open_wr: /var/backups/infodir.bak
open_wr: /var/backups/infodir.bak
-------------------------------------------------------------------------------- |
2All: so...is it safe to emerge glibc with FEATURES="-sandbox"  |
|
| Back to top |
|
|
|
Networking & Security
