[gentoo-user] emerge -eav system failed building sandbox

[gentoo-user] emerge -eav system failed building sandbox

[Mark Knecht]

Hi,
   OK, my conversion to gcc-4.1.1. seems ot have hit the skids, died,
burned up and is no longer to be foound. ;-). I came back to find the
machine back at the command line with a message:

error: C compiler cannot create executables

The screen said to attach the file

/var/tmp/portage/sandbox-1.2.17/work/build-x86-x86_64-pc-linux-gnu/config.log

to any bug reports. It's not that large so I thought I'd post it here
and see if I can get any faster answers as to what's gone wrong. To me
it looks like it's gone a bit strange about choosing the C compiler at
this point, but I don't understand why now after 2-3 hours of
compiling stuff with the new compiler.

lightning ~ # gcc-config -l
 [1] x86_64-pc-linux-gnu-3.4.6
 [2] x86_64-pc-linux-gnu-3.4.6-hardened
 [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
 [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
 [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
 [6] x86_64-pc-linux-gnu-4.1.1 *
lightning ~ #


   I am going to try an emerge --resume I suppose. I'll wait a bit for
some feedback.

Thanks,
Mark

<SNIP>

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by sandbox configure 1.2.17, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ../sandbox-1.2.17//configure --prefix=/usr
--host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib
--build=i686-pc-linux-gnu

## --------- ##
## Platform. ##
## --------- ##

hostname = lightning
uname -m = x86_64
uname -r = 2.6.17-rt5
uname -s = Linux
uname -v = #1 PREEMPT Sat Jul 1 17:02:05 PDT 2006

/usr/bin/uname -p = AMD Athlon(tm) 64 Processor 3000+
/bin/uname -X     = unknown

/bin/arch              = x86_64
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib/portage/bin
PATH: /usr/local/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1
PATH: /opt/ati/bin
PATH: /opt/ati/sbin
PATH: /opt/blackdown-jdk-1.4.2.03/bin
PATH: /opt/blackdown-jdk-1.4.2.03/jre/bin
PATH: /usr/kde/3.5/sbin
PATH: /usr/kde/3.5/bin
PATH: /usr/qt/3/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1533: checking for a BSD-compatible install
configure:1588: result: /bin/install -c
configure:1599: checking whether build environment is sane
configure:1642: result: yes
configure:1707: checking for gawk
configure:1723: found /bin/gawk
configure:1733: result: gawk
configure:1743: checking whether make sets $(MAKE)
configure:1763: result: yes
configure:1942: checking for i686-pc-linux-gnu-gcc
configure:1958: found /usr/bin/i686-pc-linux-gnu-gcc
configure:1968: result: i686-pc-linux-gnu-gcc
configure:2250: checking for C compiler version
configure:2253: i686-pc-linux-gnu-gcc --version </dev/null >&5
gcc-config error: i686-pc-linux-gnu-gcc wrapper: Unable to determine executable.
        CTARGET=i686-pc-linux-gnu
        exec=gcc

configure:2256: $? = 1
configure:2258: i686-pc-linux-gnu-gcc -v </dev/null >&5
gcc-config error: i686-pc-linux-gnu-gcc wrapper: Unable to determine executable.
        CTARGET=i686-pc-linux-gnu
        exec=gcc

configure:2261: $? = 1
configure:2263: i686-pc-linux-gnu-gcc -V </dev/null >&5
gcc-config error: i686-pc-linux-gnu-gcc wrapper: Unable to determine executable.
        CTARGET=i686-pc-linux-gnu
        exec=gcc

configure:2266: $? = 1
configure:2289: checking for C compiler default output file name
configure:2292: i686-pc-linux-gnu-gcc -march=k8 -O2 -pipe   conftest.c  >&5
gcc-config error: i686-pc-linux-gnu-gcc wrapper: Unable to determine executable.
        CTARGET=i686-pc-linux-gnu
        exec=gcc

configure:2295: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "sandbox"
| #define PACKAGE_TARNAME "sandbox"
| #define PACKAGE_VERSION "1.2.17"
| #define PACKAGE_STRING "sandbox 1.2.17"
| #define PACKAGE_BUGREPORT "sandbox@gentoo.org"
| #define PACKAGE "sandbox"
| #define VERSION "1.2.17"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2334: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-march=k8 -O2 -pipe'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=i686-pc-linux-gnu
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=i686-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_CC=i686-pc-linux-gnu-gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL}
/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/missing --run
aclocal-1.9'ALLOCA=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL}
/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/missing --run tar'
AR=''
AUTOCONF='${SHELL}
/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/missing --run
autoconf'
AUTOHEADER='${SHELL}
/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/missing --run
autoheader'
AUTOMAKE='${SHELL}
/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/missing --run
automake-1.9'
AWK='gawk'
CC='i686-pc-linux-gnu-gcc'
CCDEPMODE=''
CFLAGS='-march=k8 -O2 -pipe'
CPP=''
CPPFLAGS=''
CXXCPP=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
HAVE_RTLD_NEXT_FALSE=''
HAVE_RTLD_NEXT_TRUE=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LDFLAGS=''
LIBC_PATH=''
LIBDL=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL}
/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/missing --run
makeinfo'
OBJEXT=''
PACKAGE='sandbox'
PACKAGE_BUGREPORT='sandbox@gentoo.org'
PACKAGE_NAME='sandbox'
PACKAGE_STRING='sandbox 1.2.17'
PACKAGE_TARNAME='sandbox'
PACKAGE_VERSION='1.2.17'
PATH_SEPARATOR=':'
RANLIB=''
READELF=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='1.2.17'
ac_ct_AR=''
ac_ct_CC=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnu'
build_alias='i686-pc-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='/usr/share'
exec_prefix='NONE'
host='i686-pc-linux-gnu'
host_alias='i686-pc-linux-gnu'
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='/var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17/install-sh'
libdir='/usr/lib32'
libexecdir='${exec_prefix}/libexec'
localstatedir='/var/lib'
mandir='/usr/share/man'
mkdir_p='mkdir -p --'
oldincludedir='/usr/include'
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE "sandbox"
#define PACKAGE_BUGREPORT "sandbox@gentoo.org"
#define PACKAGE_NAME "sandbox"
#define PACKAGE_STRING "sandbox 1.2.17"
#define PACKAGE_TARNAME "sandbox"
#define PACKAGE_VERSION "1.2.17"
#define VERSION "1.2.17"

configure: exit 77
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: emerge -eav system failed building sandbox

[Mark Knecht]

On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
>    OK, my conversion to gcc-4.1.1. seems ot have hit the skids, died,
> burned up and is no longer to be foound. ;-). I came back to find the
> machine back at the command line with a message:
>
> error: C compiler cannot create executables
>
> The screen said to attach the file
>
> /var/tmp/portage/sandbox-1.2.17/work/build-x86-x86_64-pc-linux-gnu/config.log
>
> to any bug reports. It's not that large so I thought I'd post it here
> and see if I can get any faster answers as to what's gone wrong. To me
> it looks like it's gone a bit strange about choosing the C compiler at
> this point, but I don't understand why now after 2-3 hours of
> compiling stuff with the new compiler.
>
> lightning ~ # gcc-config -l
>  [1] x86_64-pc-linux-gnu-3.4.6
>  [2] x86_64-pc-linux-gnu-3.4.6-hardened
>  [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
>  [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
>  [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
>  [6] x86_64-pc-linux-gnu-4.1.1 *
> lightning ~ #
>
>
>    I am going to try an emerge --resume I suppose. I'll wait a bit for
> some feedback.
>
> Thanks,
> Mark
>
> <SNIP>
>

I tried the emerge --resume. Got the same result. Here's what I'm
seeing right now:

lightning ~ # emerge --resume
*** Resuming merge...
>>> Emerging (1 of 32) sys-apps/sandbox-1.2.17 to /
>>> checking ebuild checksums ;-)
>>> checking auxfile checksums ;-)
>>> checking miscfile checksums ;-)
>>> checking sandbox-1.2.17.tar.bz2 ;-)
>>> Unpacking source...
>>> Unpacking sandbox-1.2.17.tar.bz2 to /var/tmp/portage/sandbox-1.2.17/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sandbox-1.2.17/work/sandbox-1.2.17 ...
 * If configure fails with a 'cannot run C compiled programs' error, try this:
 * FEATURES=-sandbox emerge sandbox
 * Configuring sandbox for ABI=x86...
 * econf: updating sandbox-1.2.17/config.guess with
/usr/share/gnuconfig/config.guess
 * econf: updating sandbox-1.2.17/config.sub with
/usr/share/gnuconfig/config.sub
../sandbox-1.2.17//configure --prefix=/usr --host=i686-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32
--enable-multilib --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error:
C compiler cannot create executablesSee `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sandbox-1.2.17/work/build-x86-x86_64-pc-linux-gnu/config.log

!!! ERROR: sys-apps/sandbox-1.2.17 failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  sandbox-1.2.17.ebuild, line 84:   Called econf '--libdir=/usr/lib32'
'--enable-multilib'
  ebuild.sh, line 541:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call
stack if relevant.

lightning ~ #

Unfortunately for me I tried the command above:

FEATURES=-sandbox emerge sandbox

This failed. Bummer that I can no longer do the emerge --resume and
have it finish the emerge -eav system. Bummer, bummer, bummer......

Thanks in advance for any pointers.

Cheers,
Mark
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: emerge -eav system failed building sandbox

[Mark Knecht]

On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
> On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
> > Hi,
> >    OK, my conversion to gcc-4.1.1. seems ot have hit the skids, died,
> > burned up and is no longer to be foound. ;-). I came back to find the
> > machine back at the command line with a message:
> >
> > error: C compiler cannot create executables
> >
> > The screen said to attach the file
> >
> > /var/tmp/portage/sandbox-1.2.17/work/build-x86-x86_64-pc-linux-gnu/config.log
> >
<SNIP>

> checking for C compiler default output file name... configure: error:
> C compiler cannot create executablesSee `config.log' for more details.
>
> !!! Please attach the following file when filing a report to bugs.gentoo.org:
> !!! /var/tmp/portage/sandbox-1.2.17/work/build-x86-x86_64-pc-linux-gnu/config.log
>
> !!! ERROR: sys-apps/sandbox-1.2.17 failed.
> Call stack:
>   ebuild.sh, line 1539:   Called dyn_compile
>   ebuild.sh, line 939:   Called src_compile
>   sandbox-1.2.17.ebuild, line 84:   Called econf '--libdir=/usr/lib32'
> '--enable-multilib'
>   ebuild.sh, line 541:   Called die
>
<SNIP>

OK - known bug. I'm not smart enough to see the solution I suppose:

http://bugs.gentoo.org/show_bug.cgi?id=133209
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge -eav system failed building sandbox

[Richard Fish]

On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
> lightning ~ # gcc-config -l
>  [1] x86_64-pc-linux-gnu-3.4.6
>  [2] x86_64-pc-linux-gnu-3.4.6-hardened
>  [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
>  [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
>  [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
>  [6] x86_64-pc-linux-gnu-4.1.1 *
[snip]
>   $ ../sandbox-1.2.17//configure --prefix=/usr
> --host=i686-pc-linux-gnu --mandir=/usr/share/man
> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
> --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib
> --build=i686-pc-linux-gnu

Hmm, ok it is trying to do a multilib merge but maybe you don't have a
multilib capable compiler?

Post emerge --info and emerge -pv gcc please...

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge -eav system failed building sandbox

[Mark Knecht]

On 9/9/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
> > lightning ~ # gcc-config -l
> >  [1] x86_64-pc-linux-gnu-3.4.6
> >  [2] x86_64-pc-linux-gnu-3.4.6-hardened
> >  [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
> >  [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
> >  [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
> >  [6] x86_64-pc-linux-gnu-4.1.1 *
> [snip]
> >   $ ../sandbox-1.2.17//configure --prefix=/usr
> > --host=i686-pc-linux-gnu --mandir=/usr/share/man
> > --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
> > --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib
> > --build=i686-pc-linux-gnu
>
> Hmm, ok it is trying to do a multilib merge but maybe you don't have a
> multilib capable compiler?
>
> Post emerge --info and emerge -pv gcc please...
>
> -Richard

Hi Richard,
   Info attached.

   Note - this failed in the upgrade from gcc-3.4.6 to gcc-4.1.1.
gcc-4.1.1 got built, then doing the emerge -eav system it got built
again, and then after that sandbox fails with the messages were are
looking at.

   If it doesn't take too long, please, what is 'multilib'? I have a
full 32-bit chroot on my system since AMD64 doesn't support flash,
etc. Could this be related to that somehow?

Thanks,
Mark

lightning ~ # emerge --info
Portage 2.1-r2 (default-linux/amd64/2005.1, gcc-4.1.1, glibc-2.4-r3,
2.6.17-rt5 x86_64)
=================================================================
System uname: 2.6.17-rt5 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.12.4
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/lib/X11/xkb
/usr/lib64/mozilla/defaults/pref /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.tucdemonic.org/gentoo/
ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://mirror.gentoo.gr.jp
http://www.zentek-international.com/mirrors/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --delete-after --stats
--timeout=180 --exclude='/distfiles' --exclude='/local'
--exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage
/usr/portage/local/layman/pro-audio
/usr/portage/local/layman/pro-audio"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X alsa apache2 audiofile avi berkdb bitmap-fonts cdr cjk
cli crypt cups dlloader dri dvd dvdr dvdread emboss encode flac
fluidsynth foomaticdb fortran gif gimp gimpprint gnome gpm gstreamer
gtk gtk2 i8x0 imlib ipv6 isdnlog jack jack-tmpfs java jpeg kde ladspa
lzw lzw-tiff mjpeg mp3 mpeg mysql mythtv ncurses nls nptl nptlonly ogg
opengl pam pcre pdflib perl png ppds pppd python qt3 qt4 quicktime
radeon readline reflection sdl session sndfile spell spl ssl tcltk
tcpd tiff truetype truetype-fonts type1-fonts unicode usb v4l v4l2
vorbis xorg xpm xscreensaver xv xvid zlib elibc_glibc
input_devices_keyboard input_devices_mouse input_devices_evdev
kernel_linux userland_GNU video_cards_radeon"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL,
LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS

lightning ~ #


lightning ~ # emerge -pv gcc

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-devel/gcc-4.1.1  USE="fortran gtk nls -bootstrap
-build -doc -gcj -hardened -ip28 -ip32r10k -mudflap -multislot -nocxx
-objc -objc++ -objc-gc -test -vanilla" 0 kB

Total size of downloads: 0 kB
lightning ~ #
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge -eav system failed building sandbox

[Mark Knecht]

On 9/9/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
> > lightning ~ # gcc-config -l
> >  [1] x86_64-pc-linux-gnu-3.4.6
> >  [2] x86_64-pc-linux-gnu-3.4.6-hardened
> >  [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
> >  [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
> >  [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
> >  [6] x86_64-pc-linux-gnu-4.1.1 *
> [snip]
> >   $ ../sandbox-1.2.17//configure --prefix=/usr
> > --host=i686-pc-linux-gnu --mandir=/usr/share/man
> > --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
> > --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib
> > --build=i686-pc-linux-gnu
>
> Hmm, ok it is trying to do a multilib merge but maybe you don't have a
> multilib capable compiler?
>
> Post emerge --info and emerge -pv gcc please...
>
> -Richard
> --
> gentoo-user@gentoo.org mailing list
>
>

Richard,
   I found this report in the forums:

http://forums.gentoo.org/viewtopic-t-485514-highlight-enablemultilib.html

It points me to this thread:

http://forums.gentoo.org/viewtopic-t-495587.html

which talks about orphaned gcc files being left over from earlier
days. since I am *supposed* to have only 4.1.1 and 3.4.6 at this
point:

lightning ~ # gcc-config -l
 [1] x86_64-pc-linux-gnu-3.4.6
 [2] x86_64-pc-linux-gnu-3.4.6-hardened
 [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie
 [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp
 [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp
 [6] x86_64-pc-linux-gnu-4.1.1 *
lightning ~ #


However there is a lot of stuff hanging around right now:

lightning ~ # ls -la /usr/bin/*gcc*
-rwxr-xr-x 1 root root 11536 Sep  9 12:07 /usr/bin/gcc
lrwxrwxrwx 1 root root    62 Jun 20 18:05 /usr/bin/gcc-3.4.6 ->
/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.6/x86_64-pc-linux-gnu-gcc
lrwxrwxrwx 1 root root    62 Sep  9 12:07 /usr/bin/gcc-4.1.1 ->
/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/x86_64-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 18567 Sep  9 10:45 /usr/bin/gcc-config
-rwxr-xr-x 1 root root 11536 Sep  9 12:08 /usr/bin/gcc32
-rwxr-xr-x 1 root root 11536 Sep  9 12:08 /usr/bin/gcc64
-rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/gccbug
-rwxr-xr-x 1 root root  2050 Sep  9 14:59 /usr/bin/gccmakedep
-rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/i686-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/i686-pc-linux-gnu-gccbug
-rwxr-xr-x 1 root root 11536 Sep  9 12:07 /usr/bin/x86_64-pc-linux-gnu-gcc
lrwxrwxrwx 1 root root    62 Jun 20 18:05
/usr/bin/x86_64-pc-linux-gnu-gcc-3.4.6 ->
/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.6/x86_64-pc-linux-gnu-gcc
lrwxrwxrwx 1 root root    62 Sep  9 12:07
/usr/bin/x86_64-pc-linux-gnu-gcc-4.1.1 ->
/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/x86_64-pc-linux-gnu-gcc
-rwxr-xr-x 1 root root 11536 Sep  9 12:08 /usr/bin/x86_64-pc-linux-gnu-gcc32
-rwxr-xr-x 1 root root 11536 Sep  9 12:08 /usr/bin/x86_64-pc-linux-gnu-gcc64
-rwxr-xr-x 1 root root 18856 Mar 24 18:27 /usr/bin/x86_64-pc-linux-gnu-gccbug
lightning ~ #

   It seems that others may have fixed this by erasing the
/usr/bin/i686-pc-* files.

- Mark
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge -eav system failed building sandbox

[Richard Fish]

On 9/9/06, Mark Knecht <markknecht@gmail.com> wrote:
>    If it doesn't take too long, please, what is 'multilib'? I have a
> full 32-bit chroot on my system since AMD64 doesn't support flash,
> etc. Could this be related to that somehow?

Maybe.  Put simply, multilib is the feature of portage that rebuilds
all (most?) libraries twice, once for /lib32, and once for /lib64, to
support 32-bit and 64-bit applications respectively.

Unless you are using a no-multilib sub-profile (which you are not), it
is normal that sandbox will attempt to be built as a 32-bit version.
The problematic point seems to be this test in the sandbox
configuration:

checking for i686-pc-linux-gnu-gcc... no

If that says yes, for example because you have a cross-compiler
installed, then you can have some problems to build the 32-bit version
of sandbox.  Thus why unmerging any cross-compilers or removing any
stale i686-pc-linux-gnu-* links works around the problem.

> lightning ~ # emerge -pv gcc
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R   ] sys-devel/gcc-4.1.1  USE="fortran gtk nls -bootstrap
> -build -doc -gcj -hardened -ip28 -ip32r10k -mudflap -multislot -nocxx
> -objc -objc++ -objc-gc -test -vanilla" 0 kB

This bothers me slightly...my output has

[ebuild   R   ] sys-devel/gcc-4.1.1-r1  USE="gcj (-altivec) -bootstrap
-build -doc -fortran -gtk (-hardened) -ip28 -ip32r10k -mudflap
(-multilib) -multislot (-n32) (-n64) -nls -nocxx -objc -objc++
-objc-gc -test -vanilla" 0 kB

Notice the masked use flags multilib/n32/n64...you should be seeing
the same things regardless of the profile.  Maybe this is just due to
differences in portage versions...I'm on 2.1.1 here.

-Richard
-- 
gentoo-user@gentoo.org mailing list