Bug 25997 – glibc fails to build and ends in a sandbox violation

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description nr16020 2003-08-05 16:19:45 UTC]

emerge glibc ends by this log :
I'm using gcc 3.2.3 or 3.2.2 (I tried both), current glibc is 2.3.1-r4, trying
to upgrade to
2.3.2-r1 :
[ebuild    U ] sys-libs/glibc-2.3.2-r1 [2.3.1-r4] 

comment : may be related to http://bugs.gentoo.org/show_bug.cgi?id=25875

make[4]: Nothing to be done for `rtld-all'.
make[4]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/stdlib'
make[4]: Entering directory
`/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/string'
make[4]: Nothing to be done for `rtld-all'.
make[4]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/string'
make[3]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/elf'
gcc -nostdlib -nostartfiles -o
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/elf/sprof 
-Wl,-dynamic-linker=/lib/ld-linux.so.2   -Wl,-z,combreloc
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/csu/crt1.o
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/csu/crti.o `gcc
--print-file-name=crtbegin.o`
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/elf/sprof.o
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/dlfcn/libdl.so.2 
-Wl,-rpath-link=/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/math:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/elf:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/dlfcn:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/nss:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/nis:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/rt:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/resolv:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/crypt:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/linuxthreads
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/libc.so.6
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/libc_nonshared.a
-lgcc `gcc --print-file-name=crtend.o`
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/csu/crtn.o
gcc -nostdlib -nostartfiles -o
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/elf/lddlibc4 
-Wl,-dynamic-linker=/lib/ld-linux.so.2   -Wl,-z,combreloc
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/csu/crt1.o
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/csu/crti.o `gcc
--print-file-name=crtbegin.o`
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/elf/lddlibc4.o 
-Wl,-rpath-link=/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/math:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/elf:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/dlfcn:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/nss:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/nis:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/rt:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/resolv:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/crypt:/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/linuxthreads
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/libc.so.6
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/libc_nonshared.a
-lgcc `gcc --print-file-name=crtend.o`
/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/buildhere/csu/crtn.o
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2/elf'
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.2-r1/work/glibc-2.3.2'
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-glibc-2.3.2-r1-28017.log"

open_wr:   /var/backups/infodir.bak
--------------------------------------------------------------------------------

I don't know what to do... ideas ?

[e-mail]
EV5Junkie on freenode #gentoo

[Comment 1 nr16020 2003-08-06 01:21:53 UTC]

Tried 2.3.2-r3 and it fails in the same way.

ev5junkie, now completely clueless about the problem :/

[Comment 2 Martin Schlemmer (RETIRED) 2003-08-06 10:49:27 UTC]

*** This bug has been marked as a duplicate of 25875 ***