Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 76254 - gcc compile failing with libsandbox.so error
Summary: gcc compile failing with libsandbox.so error
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-31 10:44 UTC by James Gurney
Modified: 2004-12-31 14:18 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Gurney 2004-12-31 10:44:10 UTC
Attempting to emerge gcc. glibc and gcc-config emerged fine, but gcc errors out when attempting to link to /lib/libsandbox.so

Reproducible: Always
Steps to Reproduce:
1. emerge gcc
2. Wait until compiling errors out.

Actual Results:  
Compile stops. The following is from the config.log in
/var/tmp/portage/gcc-3.4.3/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3

configure:2390: checking for C compiler default output file name
configure:2393: /var/tmp/portage/gcc-3.4.3/work/build/gcc/xgcc
-B/var/tmp/portage/gcc-3.4.3/work/build/gcc/ -B/usr/x86_64-pc-linux-gnu/bin/
-B/usr/x86_64-pc-linux
-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem
/usr/x86_64-pc-linux-gnu/sys-include  -m32 -O2 -O2 -O2 -O2  conftest.c  >&5
configure:2396: $? = 0
configure:2442: result: a.out
configure:2447: checking whether the C compiler works
configure:2453: ./a.out
./a.out: error while loading shared libraries: /lib/libsandbox.so: cannot open
shared object file: No such file or directory
configure:2456: $? = 127
configure:2465: error: cannot run C compiled programs.

Expected Results:  
gcc should compile

I've verified that /lib/libsandbox.so exists, and I've re-merged portage. Here's
the output from ldd:

fez lib # ldd /lib/libsandbox.so
        libdl.so.2 => /lib/libdl.so.2 (0x0000002a95668000)
        libc.so.6 => /lib/libc.so.6 (0x0000002a9576a000)
        /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
(0x000000552aaaa000)

I tried adding '-sandbox' to FEATURES (found this suggestion in another bug),
and this allowed gcc to compile, but it still won't compile with sandbox enabled.

Also tried changing the CFLAGS as suggested for amd64 (CFLAGS="-march=k8 -O2
-pipe"), but this made no difference.

Output from emerge info:
Portage 2.0.51-r3 (default-linux/amd64/2004.3, gcc-3.3.3,
glibc-2.3.4.20040808-r1, 2.6.9 x86_64)
=================================================================
System uname: 2.6.9 x86_64 5
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.90.0.1.1-r3
Headers:  sys-kernel/linux-headers-2.4.21
Libtools: sys-devel/libtool-1.4.3-r3
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://gentoo.llarian.net/ ftp://gentoo.llarian.net/pub/gentoo
http://gentoo.ccccom.com ftp://gentoo.ccccom.com"
MAKEOPTS="-j 3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://gentoo.llarian.net/gentoo-portage"
USE="amd64 acpi alsa berkdb bitmap-fonts crypt f77 fortran gd gdbm gif gpm ipv6
jp2 jpeg libwww lzw lzw-tiff multilib mysql ncurses opengl oss pam pdflib perl png
 readline sdl snmp ssl tcpd tiff truetype usb userlocales xml2 xpm xrandr xv zlib"
Comment 1 Simon Stelling (RETIRED) gentoo-dev 2004-12-31 11:59:11 UTC
this is a known issue, please disable sandbox and/or usersandbox in your FEATURES= and re-emerge gcc with multilib useflag, it should work then iirc
Comment 2 James Gurney 2004-12-31 13:45:54 UTC
I've done this. As you can see from above, multilib is in my use flags. However, when I try and emerge something else, I get this error:

 * No valid multilib environment found!
 * Building without multilib support. If
 * you want to have multilib support,
 * emerge gcc with "multilib" in your
 * useflags.

Also, gcc --version shows:

gcc (GCC) 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7)

But, emerge -p gcc thinks I have 3.4.3 already:

[ebuild   R   ] sys-devel/gcc-3.4.3

Clearly I'm missing something basic here, but I don't know what it is.
Comment 3 James Gurney 2004-12-31 14:18:12 UTC
Ok, that was a case of not reading. I needed to run gcc-config. Looks ok now.