| View previous topic :: View next topic |
| Author |
Message |
grassu
Tux's lil' helper
Joined: 06 Jun 2004
Posts: 91
Location: Berlin
|
 Posted: Wed Sep 14, 2005 2:48 pm Post subject: cannot emerge after doing 2004.3-2005.0upgrade.sh |
 |
|
Hi,
I followed the 2005.0 Upgrade guide to update my system to the new profile. The script was 2004.3-2005.0upgrade.sh was successful executed (I think so, there was no visible error for me!). But when I try to "emerge -uv system" it aborts on the first package. I tried to emerge the 2 first packages by hand:
[ebuild U ] app-arch/bzip2-1.0.3-r5 [1.0.2-r4] -build -static 0 kB
[ebuild U ] app-arch/cpio-2.6-r4 [2.6-r3] +nls 0 kB
this is the output for bzip2
| Code: |
>>> emerge (1 of 1) app-arch/bzip2-1.0.3-r5 to /
>>> md5 files ;-) bzip2-1.0.3-r5.ebuild
>>> md5 files ;-) bzip2-1.0.2-r5.ebuild
>>> md5 files ;-) bzip2-1.0.3-r4.ebuild
>>> md5 files ;-) files/bzip2-1.0.2-NULL-ptr-check.patch
>>> md5 files ;-) files/bzip2-1.0.3-shared-largefile-support.patch
>>> md5 files ;-) files/bzip2-1.0.3-makefile-CFLAGS.patch
>>> md5 files ;-) files/bzip2-1.0.2-saneso.patch
>>> md5 files ;-) files/bzip2-1.0.3-saneso.patch
>>> md5 files ;-) files/bzip2-1.0.2-makefile-CFLAGS.patch
>>> md5 files ;-) files/bzip2-1.0.2-progress.patch
>>> md5 files ;-) files/digest-bzip2-1.0.2-r5
>>> md5 files ;-) files/bzip2-1.0.2-chmod.patch
>>> md5 files ;-) files/digest-bzip2-1.0.3-r5
>>> md5 files ;-) files/digest-bzip2-1.0.3-r4
>>> md5 files ;-) files/bzip2-1.0.3-no-test.patch
>>> md5 src_uri ;-) bzip2-1.0.3.tar.gz
>>> Unpacking source...
>>> Unpacking bzip2-1.0.3.tar.gz to /var/tmp/portage/bzip2-1.0.3-r5/work
* Applying bzip2-1.0.2-NULL-ptr-check.patch ... [ ok ]
* Applying bzip2-1.0.3-makefile-CFLAGS.patch ... [ ok ]
* Applying bzip2-1.0.3-saneso.patch ... [ ok ]
* Applying bzip2-1.0.3-shared-largefile-support.patch ... [ ok ]
* Applying bzip2-1.0.2-progress.patch ... [ ok ]
* Applying bzip2-1.0.2-chmod.patch ... [ ok ]
* Applying bzip2-1.0.3-no-test.patch ... [ ok ]
>>> Source unpacked.
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c blocksort.c
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c huffman.c
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c crctable.c
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c randtable.c
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c compress.c
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c decompress.c
x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC -fpic -fPIC -Wall -Winline -D_FILE_OFFSET_BITS=64 -c bzlib.c
x86_64-pc-linux-gnu-gcc -shared -Wl,-soname -Wl,libbz2.so.1 -o libbz2.so.1.0.3 blocksort.o huffman.o crctable.o randtable.o compress.o decompress.o bzlib.o
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crti.o: No such file: No such file or directory
collect2: ld returned 1 exit status
make: *** [all] Error 1
!!! ERROR: app-arch/bzip2-1.0.3-r5 failed.
!!! Function src_compile, Line 45, Exitcode 2
!!! Make failed libbz2
!!! If you need support, post the topmost build error, NOT this status message.
|
and this is for cpio:
| Code: |
>>> emerge (1 of 1) app-arch/cpio-2.6-r4 to /
>>> md5 files ;-) cpio-2.6-r3.ebuild
>>> md5 files ;-) cpio-2.6-r4.ebuild
>>> md5 files ;-) cpio-2.6-r2.ebuild
>>> md5 files ;-) files/cpio-2.6-gcc4-tests.patch
>>> md5 files ;-) files/2.6-rili-big-files.patch
>>> md5 files ;-) files/2.6-lstat.patch
>>> md5 files ;-) files/2.6-isnumber.patch
>>> md5 files ;-) files/2.6-umask.patch
>>> md5 files ;-) files/digest-cpio-2.6-r3
>>> md5 files ;-) files/digest-cpio-2.6-r2
>>> md5 files ;-) files/cpio-2.6-chmodRaceC.patch
>>> md5 files ;-) files/cpio-2.6-dirTraversal.patch
>>> md5 files ;-) files/digest-cpio-2.6-r4
>>> md5 src_uri ;-) cpio-2.6.tar.bz2
>>> Unpacking source...
>>> Unpacking cpio-2.6.tar.bz2 to /var/tmp/portage/cpio-2.6-r4/work
* Applying 2.6-rili-big-files.patch ... [ ok ]
* Applying 2.6-isnumber.patch ... [ ok ]
* Applying 2.6-umask.patch ... [ ok ]
* Applying 2.6-lstat.patch ... [ ok ]
* Applying cpio-2.6-chmodRaceC.patch ... [ ok ]
* Applying cpio-2.6-gcc4-tests.patch ... [ ok ]
* Applying cpio-2.6-dirTraversal.patch ... [ ok ]
>>> Source unpacked.
* econf: updating cpio-2.6/scripts/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating cpio-2.6/scripts/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-nls --bindir=/bin --with-rmt=/usr/sbin/rmt --libdir=/usr/lib64 --build=x86_64-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 style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/config.log
!!! ERROR: app-arch/cpio-2.6-r4 failed.
!!! Function econf, Line 496, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
|
and this is the /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/config.log:
| Code: |
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by GNU cpio configure 2.6, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-nls --bindir=/bin --with-rmt=/usr/sbin/rmt --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu
## --------- ##
## Platform. ##
## --------- ##
hostname = roberta
uname -m = x86_64
uname -r = 2.6.12-gentoo-r3
uname -s = Linux
uname -v = #2 Tue Jul 5 16:26:22 CEST 2005
/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: /sbin
PATH: /usr/sbin
PATH: /usr/lib/portage/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3-20050110
PATH: /opt/ati/bin
PATH: /opt/blackdown-jdk-1.4.2.02/bin
PATH: /opt/blackdown-jdk-1.4.2.02/jre/bin
PATH: /usr/qt/3/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1390: checking for a BSD-compatible install
configure:1445: result: /bin/install -c
configure:1456: checking whether build environment is sane
configure:1499: result: yes
configure:1564: checking for gawk
configure:1580: found /bin/gawk
configure:1590: result: gawk
configure:1600: checking whether make sets $(MAKE)
configure:1620: result: yes
configure:1811: checking for style of include used by make
configure:1839: result: GNU
configure:1872: checking for x86_64-pc-linux-gnu-gcc
configure:1888: found /usr/bin/x86_64-pc-linux-gnu-gcc
configure:1898: result: x86_64-pc-linux-gnu-gcc
configure:2180: checking for C compiler version
configure:2183: x86_64-pc-linux-gnu-gcc --version </dev/null >&5
x86_64-pc-linux-gnu-gcc (GCC) 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7)
Copyright (C) 2004 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:2186: $? = 0
configure:2188: x86_64-pc-linux-gnu-gcc -v </dev/null >&5
Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/specs
Configured with: /var/tmp/portage/gcc-3.4.3.20050110/work/gcc-3.4.3/configure --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.3-20050110 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3-20050110/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/include/g++-v3 --host=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --enable-shared --enable-threads=posix --enable-multilib --disable-libgcj --enable-languages=c,c++,f77
Thread model: posix
gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7)
configure:2191: $? = 0
configure:2193: x86_64-pc-linux-gnu-gcc -V </dev/null >&5
x86_64-pc-linux-gnu-gcc: `-V' option must have argument
configure:2196: $? = 1
configure:2219: checking for C compiler default output file name
configure:2222: x86_64-pc-linux-gnu-gcc -O3 -march=athlon64 -fomit-frame-pointer -fPIC conftest.c >&5
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:2225: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "GNU cpio"
| #define PACKAGE_TARNAME "cpio"
| #define PACKAGE_VERSION "2.6"
| #define PACKAGE_STRING "GNU cpio 2.6"
| #define PACKAGE_BUGREPORT "bug-cpio@gnu.org"
| #define PACKAGE "cpio"
| #define VERSION "2.6"
| #define _GNU_SOURCE 1
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2264: 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='-O3 -march=athlon64 -fomit-frame-pointer -fPIC'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_DEFAULT_RMT_DIR_set=
ac_cv_env_DEFAULT_RMT_DIR_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-pc-linux-gnu
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=x86_64-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_lib_nsl_gethostname=no
ac_cv_path_install='/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_CC=x86_64-pc-linux-gnu-gcc
ac_cv_prog_make_make_set=yes
## ----------------- ##
## Output variables. ##
## ----------------- ##
ACLOCAL='${SHELL} /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/missing --run aclocal-1.9'
ALLOCA=''
ALLOCA_H=''
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='${SHELL} /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/missing --run tar'
AUTOCONF='${SHELL} /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/missing --run autoconf'
AUTOHEADER='${SHELL} /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/missing --run autoheader'
AUTOM4TE=''
AUTOMAKE='${SHELL} /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/missing --run automake-1.9'
AWK='gawk'
CC='x86_64-pc-linux-gnu-gcc'
CCDEPMODE=''
CFLAGS='-O3 -march=athlon64 -fomit-frame-pointer -fPIC'
CPIO_MT_PROG=''
CPP=''
CPPFLAGS=''
CYGPATH_W='echo'
DEFAULT_RMT_COMMAND=''
DEFAULT_RMT_DIR=''
DEFS=''
DEPDIR='.deps'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
FNMATCH_H=''
GETOPT_H=''
GMSGFMT=''
HAVE__BOOL=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
INTLLIBS=''
LDFLAGS=''
LIBICONV=''
LIBINTL=''
LIBOBJS=''
LIBS=''
LTLIBICONV=''
LTLIBINTL=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/missing --run makeinfo'
MKINSTALLDIRS=''
MSGFMT=''
MSGMERGE=''
OBJEXT=''
PACKAGE='cpio'
PACKAGE_BUGREPORT='bug-cpio@gnu.org'
PACKAGE_NAME='GNU cpio'
PACKAGE_STRING='GNU cpio 2.6'
PACKAGE_TARNAME='cpio'
PACKAGE_VERSION='2.6'
PATH_SEPARATOR=':'
POSUB=''
PU_RMT_PROG=''
RANLIB=''
SET_MAKE=''
SHELL='/bin/sh'
STDBOOL_H=''
STRIP=''
SYSEXITS_H=''
USE_NLS=''
VERSION='2.6'
XGETTEXT=''
ac_ct_CC=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include='include'
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-pc-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='/usr/share'
exec_prefix='NONE'
host='x86_64-pc-linux-gnu'
host_alias='x86_64-pc-linux-gnu'
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='/var/tmp/portage/cpio-2.6-r4/work/cpio-2.6/scripts/install-sh'
libdir='/usr/lib64'
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 "cpio"
#define PACKAGE_BUGREPORT "bug-cpio@gnu.org"
#define PACKAGE_NAME "GNU cpio"
#define PACKAGE_STRING "GNU cpio 2.6"
#define PACKAGE_TARNAME "cpio"
#define PACKAGE_VERSION "2.6"
#define VERSION "2.6"
#define _GNU_SOURCE 1
configure: exit 77
|
Any help for this?
Thanks in advance,
grassu |
|
| Back to top |
|
 |
gustafson
Guru
Joined: 12 Aug 2004
Posts: 430
|
| Posted: Wed Sep 14, 2005 3:25 pm Post subject: Re: cannot emerge after doing 2004.3-2005.0upgrade.sh |
|
|
| grassu wrote: | | The script was 2004.3-2005.0upgrade.sh was successful executed (I think so, there was no visible error for me!). But when I try to "emerge -uv system" it aborts on the first package. |
I'm not certain that it worked correctly. I just went through this myself, and the script went through and did a lot of emerging on its own. I didn't watch the details too closely, however the first thing that happened is it failed wanted a gcc with multilib support. When I recompiled gcc with multilib use flag, I reran the script and it reemerge about 6 packages. Then it explicitly told me the last step to finish the upgrade, which I think was to do emerge -uv system.
If there wasn't much activity when you ran the script, I don't think it worked.
to see if you have multilib support, type "emerge -av gcc" and see if the multilib use flag is set. If not, set it and recompile gcc, the rerun the script. If you already had multilib support... well then I don't know.
When it aborts, what is the error message? |
|
| Back to top |
|
|
grassu
Tux's lil' helper
Joined: 06 Jun 2004
Posts: 91
Location: Berlin
|
| Posted: Wed Sep 14, 2005 4:08 pm Post subject: |
|
|
Ok, I put now multilib in my use flags. But when I do emerge -av gcc I get:
| Code: |
[ebuild U ] sys-devel/gcc-3.4.4-r1 [3.4.3.20050110] (-altivec) -bootstrap -boundschecking -build +fortran -gcj +gtk -hardened -ip28 (-multilib)* -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp -objc -static -vanilla 0 kB
|
Even if I do "USE=multilib emerge gcc -av" it tells me the (-multilib)*. What does this mean?
Thanks |
|
| Back to top |
|
|
gustafson
Guru
Joined: 12 Aug 2004
Posts: 430
|
| Posted: Wed Sep 14, 2005 4:18 pm Post subject: |
|
|
Very good question. The funny thing is, the exact same thing happened to me. The first time I did it, gcc was rebuilt (I assume) with multilib support since the update script didn't complain the second time I ran it. However, subsequently when I did an emerge -uavDN world, it rebuilt gcc again exactly as you described it. I was never able to figure it out. Fortunately, for me the update had already been completed and I didn't really have to worry. Sucks for you though. I'm fresh out of ideas, I guess we should wait until somebody else weighs in.
If you are just waiting... You could just rebuild it using the multilib use flag in your make.conf and ignore the verbose output. Maybe there is some sort of error that causes this confusion but isn't substantial to gcc itself? |
|
| Back to top |
|
|
grassu
Tux's lil' helper
Joined: 06 Jun 2004
Posts: 91
Location: Berlin
|
| Posted: Wed Sep 14, 2005 4:25 pm Post subject: |
|
|
Damn! Bad news. My compiler seems to be broken now!!!
Now I cannot reemerge gcc anymore. Here is the output:
| Code: |
USE=multilib emerge gcc -av
.....
......
* Configuring GCC with:
--prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/3.4.4
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.4
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.4/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.4/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/include/g++-v3
--host=x86_64-pc-linux-gnu
--build=x86_64-pc-linux-gnu
--disable-altivec
--enable-nls
--without-included-gettext
--with-system-zlib
--disable-checking
--disable-werror
--disable-libunwind-exceptions
--enable-multilib
--disable-libgcj
--enable-languages=c,c++,f77
--enable-shared
--enable-threads=posix
--enable-__cxa_atexit
--enable-clocale=gnu
creating cache ./config.cache
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking for a BSD compatible install... /bin/install -c
*** This configuration is not supported in the following subdirectories:
target-libffi target-boehm-gc target-zlib target-libjava zlib fastjar target-libobjc
(Any other directories should still work fine.)
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
*** The command 'gcc -o conftest -O2 -march=athlon64 -fPIC conftest.c' failed.
*** You must set the environment variable CC to a working compiler.
!!! ERROR: sys-devel/gcc-3.4.4-r1 failed.
!!! Function gcc_do_configure, Line 1128, Exitcode 1
!!! failed to run configure
!!! If you need support, post the topmost build error, NOT this status message.
|
I think I need help now.
Thanks,
grassu |
|
| Back to top |
|
|
gustafson
Guru
Joined: 12 Aug 2004
Posts: 430
|
| Posted: Wed Sep 14, 2005 4:31 pm Post subject: |
|
|
Oh wow, thats not good.
If you get it working again, you could try this. This was imbedded in the script telling how to install multilib support.
FEATURES=-sandbox USE=multilib emerge gcc |
|
| Back to top |
|
|
gustafson
Guru
Joined: 12 Aug 2004
Posts: 430
|
| Posted: Wed Sep 14, 2005 4:39 pm Post subject: |
|
|
Oh wow, thats not good.
If you get it working again, you could try this. This was imbedded in the script telling how to install multilib support.
FEATURES=-sandbox USE=multilib emerge gcc
more detail was in the ebuild
# if sandbox is enabled, and multilib is enabled, but we dont have a 32bit
# sandbox... installing gcc will fail as soon as it starts configuring the
# 32bit libstdc++. not fun.
if use amd64 && use multilib && hasq sandbox $FEATURES && [ ! -e /lib32/libsandbox.so ] ; then
eerror "You need a 32bit sandbox to install 32bit code with sandbox"
eerror "enabled. Either add FEATURES=-sandbox or disable multilib."
eerror "After installing a multilib gcc, you can re-emerge portage"
eerror "to get a 32bit sandbox, and this problem will go away."
ebeep
die "no 32bit sandbox"
fi |
|
| Back to top |
|
|
gustafson
Guru
Joined: 12 Aug 2004
Posts: 430
|
| Posted: Wed Sep 14, 2005 4:46 pm Post subject: |
|
|
You might have more than one compiler installed. I have two versions of gcc. They are located in
/usr/x86_64-pc-linux-gnu/gcc-bin
Perhaps you do as well and can use this? |
|
| Back to top |
|
|
grassu
Tux's lil' helper
Joined: 06 Jun 2004
Posts: 91
Location: Berlin
|
| Posted: Wed Sep 14, 2005 4:59 pm Post subject: |
|
|
yes I have in /usr/x86_64-pc-linux-gnu/gcc-bin the
3.4 and 3.4.3-20050110
but how can I tell emerge to use the 3.4 compiler? |
|
| Back to top |
|
|
grassu
Tux's lil' helper
Joined: 06 Jun 2004
Posts: 91
Location: Berlin
|
| Posted: Thu Sep 15, 2005 11:38 am Post subject: |
|
|
anyone who can help about this?
Please. |
|
| Back to top |
|
|
gustafson
Guru
Joined: 12 Aug 2004
Posts: 430
|
| Posted: Thu Sep 15, 2005 4:56 pm Post subject: |
|
|
| You might want to start a new forum about the gcc error. People with that knowledge will have probably given up on this forum topic. I would link back to this one. |
|
| Back to top |
|
|
grassu
Tux's lil' helper
Joined: 06 Jun 2004
Posts: 91
Location: Berlin
|
|
| Back to top |
|
|
|
Gentoo on AMD64
