[gentoo-user] Can't emerge sandbox

[gentoo-user] Can't emerge sandbox

[Peter Humphrey]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

Hello,

Recent versions of portage have suggested an emerge -e world, so I thought 
I'd try it. It got as far as sandbox, which failed with the once-common "C 
compiler cannot create executables" error. Of course I 
tried "FEATURES=-sandbox emerge sandbox" but that failed with the same 
error.

I wondered what is set wrongly in my environment, so I booted a minimal 
installation CD and chrooted into the system, but with the same result.

Can anyone suggest where my problem might lie? I've attached the log file. 
I'm confused by the apparent references in it to the cross-compiler. Google 
seems to have only old references.

This is a dual-Opteron box with a mostly-amd64 setup - only a few packages 
are ~amd64. I'm also running an emerge -eq world on another amd64 box, 
which has had no problem with sandbox. Same versions of portage and sandbox 
on both machines.

-- 
Rgds
Peter

[-- Attachment #2: sandbox.errlog --]
[-- Type: text/plain, Size: 7953 bytes --]

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.18.1, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ../sandbox-1.2.18.1//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 = wstn
uname -m = x86_64
uname -r = 2.6.27-gentoo-r2
uname -s = Linux
uname -v = #1 SMP Mon Nov 3 10:52:50 GMT 2008

/usr/bin/uname -p = AMD Opteron(tm) Processor 246
/bin/uname -X     = unknown

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

PATH: /usr/lib/ccache/bin
PATH: /usr/local/sbin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib64/portage/bin
PATH: /usr/local/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/i686-pc-linux-gnu/gcc-bin/4.2.2
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2
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
PATH: /opt/vmware/server/console/bin
PATH: /usr/share/karamba/bin


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

configure:1533: checking for a BSD-compatible install
configure:1588: result: /usr/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
i686-pc-linux-gnu-gcc (GCC) 4.2.2 (Gentoo 4.2.2 p1.0)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2256: $? = 0
configure:2258: i686-pc-linux-gnu-gcc -v </dev/null >&5
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /tmp/cross/i686-pc-linux-gnu/portage/cross-i686-pc-linux-gnu/gcc-4.2.2/work/gcc-4.2.2/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/i686-pc-linux-gnu/gcc-bin/4.2.2 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include/g++-v4 --host=x86_64-pc-linux-gnu --target=i686-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --disable-libmudflap --disable-libssp --disable-libgcj --with-arch=i686 --enable-languages=c,c++,fortran --with-sysroot=/usr/i686-pc-linux-gnu --disable-bootstrap --disable-libgomp --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.2.2 (Gentoo 4.2.2 p1.0)
configure:2261: $? = 0
configure:2263: i686-pc-linux-gnu-gcc -V </dev/null >&5
i686-pc-linux-gnu-gcc: '-V' must come at the start of the command line
configure:2266: $? = 1
configure:2289: checking for C compiler default output file name
configure:2292: i686-pc-linux-gnu-gcc -march=opteron -O2 -pipe   conftest.c  >&5
/usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:2295: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| 
| #define PACKAGE_NAME "sandbox"
| #define PACKAGE_TARNAME "sandbox"
| #define PACKAGE_VERSION "1.2.18.1"
| #define PACKAGE_STRING "sandbox 1.2.18.1"
| #define PACKAGE_BUGREPORT "sandbox@gentoo.org"
| #define PACKAGE "sandbox"
| #define VERSION "1.2.18.1"
| /* 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=opteron -O2 -pipe'
ac_cv_env_CPPFLAGS_set=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=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='/usr/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} /tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run aclocal-1.9'
ALLOCA=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run tar'
AR=''
AUTOCONF='${SHELL} /tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run autoconf'
AUTOHEADER='${SHELL} /tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run autoheader'
AUTOMAKE='${SHELL} /tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run automake-1.9'
AWK='gawk'
CC='i686-pc-linux-gnu-gcc'
CCDEPMODE=''
CFLAGS='-march=opteron -O2 -pipe'
CPP=''
CPPFLAGS=''
CXXCPP=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
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} /tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/missing --run makeinfo'
OBJEXT=''
PACKAGE='sandbox'
PACKAGE_BUGREPORT='sandbox@gentoo.org'
PACKAGE_NAME='sandbox'
PACKAGE_STRING='sandbox 1.2.18.1'
PACKAGE_TARNAME='sandbox'
PACKAGE_VERSION='1.2.18.1'
PATH_SEPARATOR=':'
RANLIB=''
READELF=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='1.2.18.1'
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='/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1/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.18.1"
#define PACKAGE_TARNAME "sandbox"
#define PACKAGE_VERSION "1.2.18.1"
#define VERSION "1.2.18.1"

configure: exit 77

Re: [gentoo-user] Can't emerge sandbox

[Helmut Jarausch]

On  6 Nov, Peter Humphrey wrote:
> Hello,
> 
> Recent versions of portage have suggested an emerge -e world, so I thought 
> I'd try it. It got as far as sandbox, which failed with the once-common "C 
> compiler cannot create executables" error. Of course I 
> tried "FEATURES=-sandbox emerge sandbox" but that failed with the same 
> error.
> 
> I wondered what is set wrongly in my environment, so I booted a minimal 
> installation CD and chrooted into the system, but with the same result.
> 
> Can anyone suggest where my problem might lie? I've attached the log file. 
> I'm confused by the apparent references in it to the cross-compiler. Google 
> seems to have only old references.
> 
> This is a dual-Opteron box with a mostly-amd64 setup - only a few packages 
> are ~amd64. I'm also running an emerge -eq world on another amd64 box, 
> which has had no problem with sandbox. Same versions of portage and sandbox 
> on both machines.
> 

The lines
configure:2292: i686-pc-linux-gnu-gcc -march=opteron -O2 -pipe   conftest.c  >&5
/usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status

look like a misconfigured gcc.

Can you emerge any package which requires the C-compiler?
Try 
gcc-config -l
and look which gcc is selected and if you can select a different one.
Then - with this one selected - reemerge the probably newer 
version of gcc which was broken.

I hope this helps,
Helmut.


-- 
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany

Re: [gentoo-user] Can't emerge sandbox

[Mick]

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

On Thursday 06 November 2008, Peter Humphrey wrote:
> Hello,
>
> Recent versions of portage have suggested an emerge -e world, so I thought
> I'd try it. It got as far as sandbox, which failed with the once-common "C
> compiler cannot create executables" error. Of course I
> tried "FEATURES=-sandbox emerge sandbox" but that failed with the same
> error.

Try this syntax:

FEATURES="-sandbox" emerge sandbox

Also, do you have userpriv in your portage FEATURES?  May need to remove it 
too for this purpose.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] Can't emerge sandbox

[Jorge Peixoto de Morais Neto]

On Thu, Nov 6, 2008 at 4:02 PM, Peter Humphrey <peter@humphrey.ukfsn.org> wrote:
> Hello,
>
> Recent versions of portage have suggested an emerge -e world, so I thought
> I'd try it. It got as far as sandbox, which failed with the once-common "C
> compiler cannot create executables" error. Of course I
> tried "FEATURES=-sandbox emerge sandbox" but that failed with the same
> error.
>
> I wondered what is set wrongly in my environment, so I booted a minimal
> installation CD and chrooted into the system, but with the same result.
>
> Can anyone suggest where my problem might lie? I've attached the log file.
> I'm confused by the apparent references in it to the cross-compiler. Google
> seems to have only old references.
>
> This is a dual-Opteron box with a mostly-amd64 setup - only a few packages
> are ~amd64. I'm also running an emerge -eq world on another amd64 box,
> which has had no problem with sandbox. Same versions of portage and sandbox
> on both machines.

/usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such file: No such
file or directory

Could you try
locate crt1.o
?

By the way, why are you using gcc 4.2? I would either stick with the
stable gcc 4.1 or use gcc 4.3 (which is used by a number of recent
distributions, is used even in Debian Lenny - which should be released
shortly - and has a number of improvements)

Re: [gentoo-user] Can't emerge sandbox

[Peter Humphrey]

On Thursday 06 November 2008 18:42:44 Helmut Jarausch wrote:

> The lines
> configure:2292: i686-pc-linux-gnu-gcc -march=opteron -O2 -pipe  
> conftest.c  >&5 /usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such
> file: No such file or directory collect2: ld returned 1 exit status
>
> look like a misconfigured gcc.

That was it.

> Can you emerge any package which requires the C-compiler?
> Try
> gcc-config -l

$ gcc-config -l
 [1] i686-pc-linux-gnu-4.2.2 *

 [2] x86_64-pc-linux-gnu-4.1.2 *

$ qfile i686-pc-linux-gnu-4.2.2
cross-i686-pc-linux-gnu/gcc (/etc/env.d/gcc/i686-pc-linux-gnu-4.2.2)

I did have the cross-compiler stuff installed when I was experimenting with 
distcc, but I removed it long ago. Looks like something hung on.

A simple emerge -C cross-i686-pc-linux-gnu/gcc corrected the problem, as 
now:

$ gcc-config -l
 [1] x86_64-pc-linux-gnu-4.1.2 *

...and emerge -q1 sandbox runs to completion. I still don't know though why 
only sandbox was affected - 21 other packages were merged ok.

> I hope this helps,

Certainly did - thanks. Now to figure out how to resume the emerge -e world 
from where it stopped :-)

Thanks also to the others who offered help.

-- 
Rgds
Peter

Re: [gentoo-user] Can't emerge sandbox

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

On Mon, 10 Nov 2008 09:35:27 +0000, Peter Humphrey wrote:

> Certainly did - thanks. Now to figure out how to resume the emerge -e
> world from where it stopped :-)

emerge --resume

Single package emerges don't affect the resume list.


-- 
Neil Bothwick

Do PAL taglines take up two scanlines?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]