Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Architectures & Platforms Gentoo on AMD64
  • Search

gcc 3.4.4 compile problem (on amd64)

Have an x86-64 problem? Post here.
Locked
Advanced search
18 posts • Page 1 of 1
Author
Message
bmilde
n00b
n00b
Posts: 40
Joined: Tue Aug 24, 2004 10:54 pm

gcc 3.4.4 compile problem (on amd64)

  • Quote

Post by bmilde » Tue Jul 26, 2005 12:22 pm

I couldn't compile gcc 3.4.4, it had problems with configure and it showed that this was a problem with my profile (2004.03). So I followed the steps on the guide to get 2005.0 with multilib, but I didn't compiled glib yet because I want to do that with my new compiler. I got rid of the previous error but now I got another one:

Code: Select all

/var/tmp/portage/gcc-3.4.4/work/build/gcc/xgcc -shared-libgcc -B/var/tmp/portage/gcc-3.4.4/work/build/gcc/ -nostdinc++ -L/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3/src -L/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs -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 -shared -nostdlib /usr/lib/gcc/x86_64-pc-linux-gnu/../../../lib32/crti.o /var/tmp/portage/gcc-3.4.4/work/build/gcc/32/crtbeginS.o  .libs/allocator.o .libs/codecvt.o .libs/complex_io.o .libs/ctype.o .libs/debug.o .libs/debug_list.o .libs/functexcept.o .libs/globals_locale.o .libs/globals_io.o .libs/ios.o .libs/ios_failure.o .libs/ios_init.o .libs/ios_locale.o .libs/limits.o .libs/list.o .libs/locale.o .libs/locale_init.o .libs/locale_facets.o .libs/localename.o .libs/stdexcept.o .libs/strstream.o .libs/tree.o .libs/allocator-inst.o .libs/concept-inst.o .libs/fstream-inst.o .libs/ext-inst.o .libs/io-inst.o .libs/istream-inst.o .libs/locale-inst.o .libs/locale-misc-inst.o .libs/misc-inst.o .libs/ostream-inst.o .libs/sstream-inst.o .libs/streambuf-inst.o .libs/string-inst.o .libs/valarray-inst.o .libs/wlocale-inst.o .libs/wstring-inst.o .libs/atomicity.o .libs/codecvt_members.o .libs/collate_members.o .libs/ctype_members.o .libs/messages_members.o .libs/monetary_members.o .libs/numeric_members.o .libs/time_members.o .libs/basic_file.o .libs/c++locale.o -Wl,--whole-archive ../libmath/.libs/libmath.a ../libsupc++/.libs/libsupc++convenience.a -Wl,--no-whole-archive  -L/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3/src -L/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs -lm ../libmath/.libs/libmath.a ../libsupc++/.libs/libsupc++convenience.a -L/var/tmp/portage/gcc-3.4.4/work/build/gcc/32 -L/var/tmp/portage/gcc-3.4.4/work/build/gcc -L/usr/x86_64-pc-linux-gnu/bin -L/usr/x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/../../../x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/../../../lib32 -L/usr/lib/gcc/x86_64-pc-linux-gnu/../.. -L/lib/../lib32 -L/usr/lib/../lib32 -lgcc_s_32 -lc -lgcc_s_32 -lgcc_s_32 -lc -lgcc_s_32 /var/tmp/portage/gcc-3.4.4/work/build/gcc/32/crtendS.o /usr/lib/gcc/x86_64-pc-linux-gnu/../../../lib32/crtn.o  -Wl,-O1 -Wl,--version-script=libstdc++-symbol.ver -Wl,-soname -Wl,libstdc++.so.6 -o .libs/libstdc++.so.6.0.3
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/../../libm.so when searching for -lm
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/../../libm.a when searching for -lm
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/../../libm.so when searching for -lm
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/../../libm.a when searching for -lm
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
/usr/x86_64-pc-linux-gnu/bin/ld: cannot find -lm
collect2: ld returned 1 exit status
make[7]: *** [libstdc++.la] Fehler 1
make[7]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3/src'
make[6]: *** [all-recursive] Fehler 1
make[6]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3'
make[5]: *** [all] Fehler 2
make[5]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/32/libstdc++-v3'
make[4]: *** [multi-do] Fehler 1
make[4]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/libstdc++-v3'
make[3]: *** [all-multi] Fehler 2
make[3]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/libstdc++-v3'
make[2]: *** [all] Fehler 2
make[2]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build/x86_64-pc-linux-gnu/libstdc++-v3'
make[1]: *** [all-target-libstdc++-v3] Fehler 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4/work/build'
make: *** [profiledbootstrap] Fehler 2

!!! ERROR: sys-devel/gcc-3.4.4 failed.
!!! Function gcc_do_make, Line 1214, Exitcode 2
!!! emake failed with profiledbootstrap
!!! If you need support, post the topmost build error, NOT this status message.
I compile gcc 3.4.4 with USE="multilib"
nasenbaer Incoming # USE="multilib" emerge --verbose --pretend gcc

Code: Select all

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild     U ] sys-devel/gcc-3.4.4 [3.4.3.20050110-r2] (-altivec) -bootstrap -boundschecking -build +fortran -gcj +gtk -hardened -ip28 (-multilib)* -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp -objc -static 0 kB

Total size of downloads: 0 kB
What does (-multilib)* mean?

gcc-config -l shows me

Code: Select all

[1] x86_64-pc-linux-gnu-3.4.2
[2] x86_64-pc-linux-gnu-3.4.2-hardened
[3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
[4] x86_64-pc-linux-gnu-3.4.3-20050110 *
[5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened
[6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie
[7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
and I use this version of binutils, if it does matter in this case: [1] x86_64-pc-linux-gnu-2.16.1 *

Can someone help me with this problem? Very nasty if you can't get your compiler compiled and also it takes much time to get this error message because before it compiles and compiles...

B. Milde
Top
OldTango
l33t
l33t
User avatar
Posts: 739
Joined: Sat Feb 21, 2004 5:08 pm
Contact:
Contact OldTango
Website

  • Quote

Post by OldTango » Wed Jul 27, 2005 12:41 am

First off multilib is forced on the amd64 2005.0 profile so the (-multilib)* means nothing. I am assumeing it is because you have multilib set in your use flags.

I can not tell you how may errors I have gotten upgrading to the 2005.0 profile. I have gone back and forth at least 15 times. You can read some of it here. The forums are loaded with these kinds of gcc errors as well as with glibc. The only thing most have in common is that its usually amd64 using the 2005.0 multilib profile.

I can build both gcc and glibc under the 2004.3 profile at will, but switching to the 2005.0 profile usually causes all kinds of strange and wierd errors. I would be willing to bet most everybody will get c compilier errors when updating sandbox.

The only advise I can offer you is to go back to the 2004.3 profile and follow the amd64 2005.0 upgrade guide, update the necessary files, rebuild gcc than glibc and then move to the 2005.0 profile. This may not completely solve emerge errors. I have a strong feeling there is something broked, but I have been unable to find the problem yet.
Top
bmilde
n00b
n00b
Posts: 40
Joined: Tue Aug 24, 2004 10:54 pm

  • Quote

Post by bmilde » Wed Jul 27, 2005 3:15 pm

I have managed to compile gcc 3.4.4. I played a bit with it, followed the guidlines etc and I had to compile glibc before gcc. You're right some strange things happened with 2004.03 -> 2005.0. I have many emerge error and had to reemerge many packages (qt,kdelibs) to get rid of them :-(
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Wed Jul 27, 2005 7:35 pm

Well, you went out of order. It looks like youu changed the make.profile symlink before you should have. The upgrade guide order is very important. Please use the script in portage/profiles/default-linux/amd64/2005.0/scripts or use the Upgrade Guide.

Do the following to clean this up and upgrade properly:

# rm -rf /lib32 /usr/lib32
# rm /etc/make.profile
# ln -s /usr/portage/profiles/default-linux/amd64/2004.3 /etc/make.profile
# emerge --sync
# emerge -v --oneshot '>=emul-linux-x86-glibc-2.3.4.20041102'
# rm -rf /var/tmp/2005.0_upgrade
# cd /usr/portage/profiles/default-linux/amd64/2005.0/scripts
# ./2004.3-2005.0upgrade.sh
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
OldTango
l33t
l33t
User avatar
Posts: 739
Joined: Sat Feb 21, 2004 5:08 pm
Contact:
Contact OldTango
Website

  • Quote

Post by OldTango » Wed Jul 27, 2005 11:46 pm

The last time I did the upgrade I followed the guide exactly as it was written, taking in to accout I had already done several emerge updates after my first update a couple of months ago. It wasn't untill the new emul/libs were added that I could get glibc to compile at all. My system seems ok and stable. It is only sandbox updates that cause an error and it is always the same error in the exact same place.

Code: Select all

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.
the config log as always reads

Code: Select all

configure:2287: checking for C compiler default output file name
configure:2290: x86_64-pc-linux-gnu-gcc -O3 -march=k8 -pipe -fomit-frame-pointer -DSB_HAVE_64BIT_ARCH   conftest.c  >&5
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find /emul/linux/x86/lib/libc.so.6
collect2: ld returned 1 exit status
configure:2293: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "sandbox"
| #define PACKAGE_TARNAME "sandbox"
| #define PACKAGE_VERSION "1.2.11"
| #define PACKAGE_STRING "sandbox 1.2.11"
| #define PACKAGE_BUGREPORT "dev-portage@gentoo.org"
| #define PACKAGE "sandbox"
| #define VERSION "1.2.11"
| /* end confdefs.h.  */
it appears not be able to locate /emul/linux/x86/lib/libc.so.6 which on my system is located /emul/linux/x86/lib/lib32 where the lib32 is a symlink pointing back to /emul/linux/x86/lib/. Inside /emul/linux/x86/lib/lib32 is libc.so.6, a symlink pointing to /emul/linux/x86/lib/lib32/libc-2.3.5.so

How confusing is this.........................................:lol:

Maybe I have some stale libs or something, but even after a successful upgrade to the 2005.0 profile sandbox updates always fail in this spot.

I can attempt the upgarde once more using the script like you ask. I have done it so many times I can almost recall every step from memory. I just don't understand how I might have missed something.
Top
Albert_Alligator
Apprentice
Apprentice
User avatar
Posts: 193
Joined: Wed May 12, 2004 3:09 pm
Location: Okefenokee Swamp
Contact:
Contact Albert_Alligator
Website

  • Quote

Post by Albert_Alligator » Thu Jul 28, 2005 4:41 am

eradicator wrote:Well, you went out of order. It looks like youu changed the make.profile symlink before you should have. The upgrade guide order is very important. Please use the script in portage/profiles/default-linux/amd64/2005.0/scripts or use the Upgrade Guide.

Do the following to clean this up and upgrade properly:

# rm -rf /lib32 /usr/lib32
# rm /etc/make.profile
# ln -s /usr/portage/profiles/default-linux/amd64/2004.3 /etc/make.profile
# emerge --sync
# emerge -v --oneshot '>=emul-linux-x86-glibc-2.3.4.20041102'
# rm -rf /var/tmp/2005.0_upgrade
# cd /usr/portage/profiles/default-linux/amd64/2005.0/scripts
# ./2004.3-2005.0upgrade.sh
Ok, followed your instructions to the tee, also, I wasn't upgrading from 2004 to 2005...I started off with 2005.

I'm getting this when I run the script:

Code: Select all

Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/portage-2.0.51.22-r2 to /
>>> md5 files   ;-) portage-2.0.51.22-r2.ebuild
>>> md5 files   ;-) portage-2.0.51.19.ebuild
>>> md5 files   ;-) files/05portage.envd
>>> md5 files   ;-) files/2.0.51.22-fixes.patch
>>> md5 files   ;-) files/digest-portage-2.0.51.19
>>> md5 files   ;-) files/README.RESCUE
>>> md5 files   ;-) files/digest-portage-2.0.51.22-r2
>>> md5 src_uri ;-) portage-2.0.51.22.tar.bz2
>>> Unpacking source...
>>> Unpacking portage-2.0.51.22.tar.bz2 to /var/tmp/portage/portage-2.0.51.22-r2/work
patching file ChangeLog
patching file bin/ebuild.sh
patching file bin/emake
patching file bin/emerge
patching file bin/repoman
patching file pym/portage.py
>>> Source unpacked.
Listing /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/cvstree.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/dcdialog.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/dispatch_conf.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/emergehelp.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/getbinpkg.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/output.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_checksum.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_const.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_contents.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_data.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_db_anydbm.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_db_cpickle.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_db_flat.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_db_template.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_db_test.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_dep.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_exception.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_exec.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_file.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_gpg.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_localization.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_locks.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/portage_util.py ...
Compiling /var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/pym/xpak.py ...
{standard input}: Assembler messages:
{standard input}:25: Error: bad register name `%rsp'
{standard input}:27: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:28: Error: bad register name `%rdi'
{standard input}:33: Error: bad register name `%rsp'
{standard input}:43: Error: bad register name `%r12'
{standard input}:45: Error: bad register name `%rdi'
{standard input}:46: Error: bad register name `%rbp'
{standard input}:48: Error: bad register name `%rsi'
{standard input}:49: Error: bad register name `%rbx'
{standard input}:52: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:53: Error: bad register name `%r12'
{standard input}:57: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:59: Error: `movslq' is only supported in 64-bit mode
{standard input}:60: Error: bad register name `%rbp'
{standard input}:65: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:66: Error: bad register name `%r12'
{standard input}:70: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:72: Error: `movslq' is only supported in 64-bit mode
{standard input}:73: Error: bad register name `%rbp'
{standard input}:78: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:79: Error: bad register name `%r12'
{standard input}:83: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:85: Error: `movslq' is only supported in 64-bit mode
{standard input}:86: Error: bad register name `%rbp'
{standard input}:91: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:92: Error: bad register name `%r12'
{standard input}:96: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:98: Error: `movslq' is only supported in 64-bit mode
{standard input}:99: Error: bad register name `%rbp'
{standard input}:106: Error: bad register name `%rbx'
{standard input}:107: Error: bad register name `%rbp'
{standard input}:108: Error: bad register name `%r12'
{standard input}:117: Error: bad register name `%r13'
{standard input}:119: Error: bad register name `%rsi'
{standard input}:120: Error: bad register name `%r12'
{standard input}:122: Error: bad register name `%rdi'
{standard input}:123: Error: bad register name `%rbp'
{standard input}:126: Error: bad register name `%rbx'
{standard input}:128: Error: bad register name `%rsp'
{standard input}:138: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:140: Error: bad register name `%r12'
{standard input}:144: Error: `movslq' is only supported in 64-bit mode
{standard input}:148: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:149: Error: `movslq' is only supported in 64-bit mode
{standard input}:150: Error: bad register name `%r13'
{standard input}:157: Error: bad register name `%rsp'
{standard input}:158: Error: bad register name `%rbx'
{standard input}:159: Error: bad register name `%rbp'
{standard input}:160: Error: bad register name `%r12'
{standard input}:161: Error: bad register name `%r13'
{standard input}:200: Error: bad register name `%rbx'
{standard input}:202: Error: bad register name `%rbp'
{standard input}:204: Error: bad register name `%rsi'
{standard input}:205: Error: bad register name `%r12'
{standard input}:207: Error: bad register name `%r13'
{standard input}:209: Error: bad register name `%rsp'
{standard input}:216: Error: `myname(%rip)' is not a valid base/index expression
{standard input}:225: Error: bad register name `%rsi)'
{standard input}:233: Error: `myname(%rip)' is not a valid base/index expression
{standard input}:235: Error: bad register name `%rdx'
{standard input}:245: Error: bad register name `%rax'
{standard input}:246: Error: bad register name `%rax'
{standard input}:250: Error: bad register name `%rax'
{standard input}:251: Error: bad register name `%rax'
{standard input}:253: Error: bad register name `%rbx)'
{standard input}:257: Error: bad register name `%r9'
{standard input}:263: Error: bad register name `%r9'
{standard input}:267: Error: bad register name `%rbx)'
{standard input}:268: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:273: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:274: Error: bad register name `%rbx)'
{standard input}:276: Error: bad register name `%rdx)'
{standard input}:277: Error: bad register name `%rax'
{standard input}:281: Error: bad register name `%rbx)'
{standard input}:284: Error: bad register name `%rbx)'
{standard input}:285: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:290: Error: bad register name `%rbx)'
{standard input}:293: Error: bad register name `%rbx)'
{standard input}:296: Error: bad register name `%rax'
{standard input}:297: Error: bad register name `%rax'
{standard input}:300: Error: bad register name `%rsi'
{standard input}:301: Error: bad register name `%rax'
{standard input}:303: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:308: Error: `endbuf+4(%rip)' is not a valid base/index expression
{standard input}:310: Error: `endbuf+5(%rip)' is not a valid base/index expression
{standard input}:313: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:315: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:317: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:319: Error: bad register name `%rbx)'
{standard input}:320: Error: `myname(%rip)' is not a valid base/index expression
{standard input}:324: Error: bad register name `%rbx)'
{standard input}:325: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:330: Error: bad register name `%rbx)'
{standard input}:331: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:336: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:338: Error: `movzbq' is only supported in 64-bit mode
{standard input}:339: Error: bad register name `%r10b'
{standard input}:340: Error: `movzbq' is only supported in 64-bit mode
{standard input}:341: Error: bad register name `%r9b'
{standard input}:342: Error: `movzbq' is only supported in 64-bit mode
{standard input}:343: Error: bad register name `%r8b'
{standard input}:344: Error: bad register name `%rdx)'
{standard input}:345: Error: `endbuf+4(%rip)' is not a valid base/index expression
{standard input}:346: Error: `endbuf+5(%rip)' is not a valid base/index expression
{standard input}:347: Error: `endbuf+6(%rip)' is not a valid base/index expression
{standard input}:348: Error: `endbuf+7(%rip)' is not a valid base/index expression
{standard input}:349: Error: bad register name `%bpl'
{standard input}:350: Error: bad register name `%rbx)'
{standard input}:354: Error: bad register name `%rbx)'
{standard input}:357: Error: bad register name `%rbx)'
{standard input}:360: Error: bad register name `%rax'
{standard input}:361: Error: bad register name `%rax'
{standard input}:363: Error: bad register name `%rbx)'
{standard input}:366: Error: bad register name `%rax'
{standard input}:367: Error: bad register name `%rax'
{standard input}:369: Error: bad register name `%rbx)'
{standard input}:372: Error: bad register name `%rax'
{standard input}:373: Error: bad register name `%rax'
{standard input}:374: Error: bad register name `%rax'
{standard input}:376: Error: `dbfile(%rip)' is not a valid base/index expression
{standard input}:378: Error: `datafile(%rip)' is not a valid base/index expression
{standard input}:381: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:383: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:385: Error: bad register name `%rbx)'
{standard input}:387: Error: `myname(%rip)' is not a valid base/index expression
{standard input}:391: Error: bad register name `%rbx)'
{standard input}:393: Error: `myname(%rip)' is not a valid base/index expression
{standard input}:397: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:402: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:405: Error: `myname(%rip)' is not a valid base/index expression
{standard input}:412: Error: bad register name `%rax'
{standard input}:414: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:418: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:420: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:422: Error: bad register name `%rbx)'
{standard input}:426: Error: bad register name `%rbx)'
{standard input}:429: Error: `endbuf+6(%rip)' is not a valid base/index expression
{standard input}:432: Error: `endbuf+7(%rip)' is not a valid base/index expression
{standard input}:434: Error: `endbuf+1(%rip)' is not a valid base/index expression
{standard input}:435: Error: `movsbq' is only supported in 64-bit mode
{standard input}:437: Error: `endbuf+2(%rip)' is not a valid base/index expression
{standard input}:438: Error: `movzbq' is only supported in 64-bit mode
{standard input}:440: Error: bad register name `%r12'
{standard input}:441: Error: `movslq' is only supported in 64-bit mode
{standard input}:443: Error: bad register name `%rbx)'
{standard input}:444: Error: bad register name `%r12'
{standard input}:445: Error: `cltq' is only supported in 64-bit mode
{standard input}:446: Error: bad register name `%r11'
{standard input}:447: Error: bad register name `%rax'
{standard input}:448: Error: bad register name `%rdx'
{standard input}:450: Error: bad register name `%rax'
{standard input}:451: Error: bad register name `%rax'
{standard input}:453: Error: bad register name `%rbx)'
{standard input}:456: Error: bad register name `%rax'
{standard input}:457: Error: bad register name `%rax'
{standard input}:459: Error: `datafile(%rip)' is not a valid base/index expression
{standard input}:461: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:465: Error: `datafile(%rip)' is not a valid base/index expression
{standard input}:468: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:470: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:472: Error: bad register name `%rbx)'
{standard input}:475: Error: `datafile(%rip)' is not a valid base/index expression
{standard input}:477: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:478: Error: bad register name `%r12'
{standard input}:482: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:484: Error: `movslq' is only supported in 64-bit mode
{standard input}:485: Error: bad register name `%rbp'
{standard input}:490: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:491: Error: bad register name `%r12'
{standard input}:495: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:496: Error: bad register name `%r13d'
{standard input}:497: Error: `movslq' is only supported in 64-bit mode
{standard input}:498: Error: bad register name `%rbp'
{standard input}:501: Error: bad register name `%r13d'
{standard input}:503: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:504: Error: bad register name `%r12'
{standard input}:508: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:510: Error: `movslq' is only supported in 64-bit mode
{standard input}:511: Error: bad register name `%rbp'
{standard input}:516: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:517: Error: bad register name `%r12'
{standard input}:521: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:522: Error: bad register name `%r13d'
{standard input}:523: Error: `movslq' is only supported in 64-bit mode
{standard input}:524: Error: bad register name `%rbp'
{standard input}:527: Error: bad register name `%r13d'
{standard input}:530: Error: `dbfile(%rip)' is not a valid base/index expression
{standard input}:531: Error: `outfile(%rip)' is not a valid base/index expression
{standard input}:533: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:534: Error: bad register name `%rbp'
{standard input}:538: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:539: Error: bad register name `%r13d'
{standard input}:540: Error: `movslq' is only supported in 64-bit mode
{standard input}:541: Error: bad register name `%r12'
{standard input}:544: Error: bad register name `%r13d'
{standard input}:546: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:547: Error: bad register name `%rbp'
{standard input}:551: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:553: Error: `movslq' is only supported in 64-bit mode
{standard input}:554: Error: bad register name `%r12'
{standard input}:559: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:560: Error: bad register name `%rbp'
{standard input}:564: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:565: Error: bad register name `%r13d'
{standard input}:566: Error: `movslq' is only supported in 64-bit mode
{standard input}:567: Error: bad register name `%r12'
{standard input}:570: Error: bad register name `%r13d'
{standard input}:572: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:573: Error: bad register name `%rbp'
{standard input}:577: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:579: Error: `movslq' is only supported in 64-bit mode
{standard input}:580: Error: bad register name `%r12'
{standard input}:586: Error: `outfile(%rip)' is not a valid base/index expression
{standard input}:591: Error: `outfile(%rip)' is not a valid base/index expression
{standard input}:594: Error: `dbfile(%rip)' is not a valid base/index expression
{standard input}:596: Error: `datafile(%rip)' is not a valid base/index expression
{standard input}:598: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:600: Error: `mystat(%rip)' is not a valid base/index expression
{standard input}:605: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:608: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:610: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:611: Error: `insize(%rip)' is not a valid base/index expression
{standard input}:612: Error: `seekto(%rip)' is not a valid base/index expression
{standard input}:613: Error: `datafile(%rip)' is not a valid base/index expression
{standard input}:614: Error: bad register name `%r12'
{standard input}:615: Error: bad register name `%rsi)'
{standard input}:621: Error: bad register name `%r8d'
{standard input}:623: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:624: Error: bad register name `%r8d'
{standard input}:626: Error: bad register name `%r8d'
{standard input}:627: Error: bad register name `%r8d'
{standard input}:628: Error: `movslq' is only supported in 64-bit mode
{standard input}:629: Error: bad register name `%r12'
{standard input}:633: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:635: Error: `movslq' is only supported in 64-bit mode
{standard input}:636: Error: bad register name `%r13'
{standard input}:641: Error: `seekto(%rip)' is not a valid base/index expression
{standard input}:642: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:644: Error: bad register name `%rsi'
{standard input}:645: Error: bad register name `%rsi'
{standard input}:647: Error: `infile(%rip)' is not a valid base/index expression
{standard input}:648: Error: `insize(%rip)' is not a valid base/index expression
{standard input}:649: Error: `dbfile(%rip)' is not a valid base/index expression
{standard input}:650: Error: bad register name `%r12'
{standard input}:657: Error: bad register name `%r10d'
{standard input}:658: Error: bad register name `%r9d'
{standard input}:659: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:660: Error: bad register name `%r10d'
{standard input}:661: Error: bad register name `%r12'
{standard input}:663: Error: bad register name `%r10d'
{standard input}:664: Error: bad register name `%r10d'
{standard input}:665: Error: `movslq' is only supported in 64-bit mode
{standard input}:669: Error: `mybuf(%rip)' is not a valid base/index expression
{standard input}:671: Error: `movslq' is only supported in 64-bit mode
{standard input}:672: Error: bad register name `%r13'
{standard input}:677: Error: `infile(%rip)' is not a valid base/index expression
>>> Test phase [not enabled]: sys-apps/portage-2.0.51.22-r2

>>> Install portage-2.0.51.22-r2 into /var/tmp/portage/portage-2.0.51.22-r2/image/ category sys-apps
install: cannot stat `/var/tmp/portage/portage-2.0.51.22-r2/work/portage-2.0.51.22/src/tbz2tool': No such file or directory
man:
prepallstrip:
strip: x86_64-pc-linux-gnu-strip --strip-unneeded
strip: x86_64-pc-linux-gnu-strip --strip-unneeded
   usr/lib/portage/bin/tbz2tool
>>> Completed installing portage-2.0.51.22-r2 into /var/tmp/portage/portage-2.0.51.22-r2/image/

>>> Merging sys-apps/portage-2.0.51.22-r2 to /
--- /etc/
>>> /etc/make.globals
--- /etc/env.d/
>>> /etc/env.d/05portage.envd
>>> /etc/etc-update.conf
>>> /etc/dispatch-conf.conf
>>> /etc/make.conf.example
--- /usr/
--- /usr/bin/
>>> /usr/bin/xpak -> ../lib/portage/bin/xpak
>>> /usr/bin/repoman -> ../lib/portage/bin/repoman
>>> /usr/bin/portageq -> ../lib/portage/bin/portageq
>>> /usr/bin/ebuild -> ../lib/portage/bin/ebuild
>>> /usr/bin/emerge -> ../lib/portage/bin/emerge
>>> /usr/bin/tbz2tool -> ../lib/portage/bin/tbz2tool
--- /usr/lib/
--- /usr/lib/portage/
--- /usr/lib/portage/bin/
>>> /usr/lib/portage/bin/fixpackages
>>> /usr/lib/portage/bin/domo
>>> /usr/lib/portage/bin/xpak
>>> /usr/lib/portage/bin/fix-db.py
>>> /usr/lib/portage/bin/dolib.so
>>> /usr/lib/portage/bin/donewins -> newins
>>> /usr/lib/portage/bin/mirror.py
>>> /usr/lib/portage/bin/env-update
>>> /usr/lib/portage/bin/fixdbentries
>>> /usr/lib/portage/bin/repoman
>>> /usr/lib/portage/bin/dopython
>>> /usr/lib/portage/bin/dobin
>>> /usr/lib/portage/bin/dodir
>>> /usr/lib/portage/bin/dodoc
>>> /usr/lib/portage/bin/doexe
>>> /usr/lib/portage/bin/dojar
>>> /usr/lib/portage/bin/doins
>>> /usr/lib/portage/bin/dolib
>>> /usr/lib/portage/bin/doman
>>> /usr/lib/portage/bin/dosed
>>> /usr/lib/portage/bin/dosym
>>> /usr/lib/portage/bin/emake
>>> /usr/lib/portage/bin/etc-update
>>> /usr/lib/portage/bin/portage_gpg_update.sh
>>> /usr/lib/portage/bin/doconfd
>>> /usr/lib/portage/bin/doinitd
>>> /usr/lib/portage/bin/dolib.a
>>> /usr/lib/portage/bin/emerge-webrsync
>>> /usr/lib/portage/bin/regenworld
>>> /usr/lib/portage/bin/chkcontents
>>> /usr/lib/portage/bin/portageq
>>> /usr/lib/portage/bin/clean_locks
>>> /usr/lib/portage/bin/pemerge.py
>>> /usr/lib/portage/bin/prepstrip
>>> /usr/lib/portage/bin/archive-conf
>>> /usr/lib/portage/bin/ebuild
>>> /usr/lib/portage/bin/doenvd
>>> /usr/lib/portage/bin/dohard
>>> /usr/lib/portage/bin/dohtml
>>> /usr/lib/portage/bin/doinfo
>>> /usr/lib/portage/bin/dosbin
>>> /usr/lib/portage/bin/emerge
>>> /usr/lib/portage/bin/fowners
>>> /usr/lib/portage/bin/fperms
>>> /usr/lib/portage/bin/newenvd
>>> /usr/lib/portage/bin/newsbin
>>> /usr/lib/portage/bin/prepallman
>>> /usr/lib/portage/bin/pkgmerge.new
>>> /usr/lib/portage/bin/newbin
>>> /usr/lib/portage/bin/newdoc
>>> /usr/lib/portage/bin/newexe
>>> /usr/lib/portage/bin/newins
>>> /usr/lib/portage/bin/newman
>>> /usr/lib/portage/bin/dispatch-conf
>>> /usr/lib/portage/bin/md5check.py
>>> /usr/lib/portage/bin/md5check.sh
>>> /usr/lib/portage/bin/ebuild.sh
>>> /usr/lib/portage/bin/preplib.so
>>> /usr/lib/portage/bin/pkgmerge
>>> /usr/lib/portage/bin/prepinfo
>>> /usr/lib/portage/bin/prepallstrip
>>> /usr/lib/portage/bin/newconfd
>>> /usr/lib/portage/bin/newinitd
>>> /usr/lib/portage/bin/newlib.a
>>> /usr/lib/portage/bin/quickpkg
>>> /usr/lib/portage/bin/prepalldocs
>>> /usr/lib/portage/bin/prepallinfo
>>> /usr/lib/portage/bin/env-update.sh
>>> /usr/lib/portage/bin/pkgname
>>> /usr/lib/portage/bin/newlib.so
>>> /usr/lib/portage/bin/find-requires
>>> /usr/lib/portage/bin/tbz2tool
>>> /usr/lib/portage/bin/prepall
>>> /usr/lib/portage/bin/preplib
>>> /usr/lib/portage/bin/prepman
--- /usr/lib/portage/pym/
>>> /usr/lib/portage/pym/portage_const.py
>>> /usr/lib/portage/pym/portage_db_anydbm.py
>>> /usr/lib/portage/pym/xpak.pyo
>>> /usr/lib/portage/pym/xpak.py
>>> /usr/lib/portage/pym/portage_db_cpickle.pyo
>>> /usr/lib/portage/pym/cvstree.pyo
>>> /usr/lib/portage/pym/portage.py
>>> /usr/lib/portage/pym/portage_dep.py
>>> /usr/lib/portage/pym/portage_db_test.py
>>> /usr/lib/portage/pym/output.pyo
>>> /usr/lib/portage/pym/portage_exception.py
>>> /usr/lib/portage/pym/portage_data.py
>>> /usr/lib/portage/pym/portage.py.rej
>>> /usr/lib/portage/pym/portage_db_flat.py
>>> /usr/lib/portage/pym/portage_gpg.py
>>> /usr/lib/portage/pym/portage_locks.py
>>> /usr/lib/portage/pym/portage_dep.pyo
>>> /usr/lib/portage/pym/portage_checksum.py
>>> /usr/lib/portage/pym/dispatch_conf.py
>>> /usr/lib/portage/pym/portage_db_template.pyo
>>> /usr/lib/portage/pym/portage_exec.pyo
>>> /usr/lib/portage/pym/dcdialog.py
>>> /usr/lib/portage/pym/portage_db_test.pyo
>>> /usr/lib/portage/pym/portage_contents.pyo
>>> /usr/lib/portage/pym/portage_const.pyo
>>> /usr/lib/portage/pym/portage_contents.py
>>> /usr/lib/portage/pym/emergehelp.pyo
>>> /usr/lib/portage/pym/portage_db_anydbm.pyo
>>> /usr/lib/portage/pym/portage_localization.py
>>> /usr/lib/portage/pym/portage_util.pyo
>>> /usr/lib/portage/pym/portage_db_cpickle.py
>>> /usr/lib/portage/pym/portage_file.py
>>> /usr/lib/portage/pym/getbinpkg.py
>>> /usr/lib/portage/pym/portage_checksum.pyo
>>> /usr/lib/portage/pym/dcdialog.pyo
>>> /usr/lib/portage/pym/portage_exception.pyo
>>> /usr/lib/portage/pym/portage_localization.pyo
>>> /usr/lib/portage/pym/portage_data.pyo
>>> /usr/lib/portage/pym/portage_exec.py
>>> /usr/lib/portage/pym/cvstree.py
>>> /usr/lib/portage/pym/output.py
>>> /usr/lib/portage/pym/portage.pyo
>>> /usr/lib/portage/pym/portage_db_flat.pyo
>>> /usr/lib/portage/pym/dispatch_conf.pyo
>>> /usr/lib/portage/pym/emergehelp.py
>>> /usr/lib/portage/pym/portage_db_template.py
>>> /usr/lib/portage/pym/portage_gpg.pyo
>>> /usr/lib/portage/pym/portage_locks.pyo
>>> /usr/lib/portage/pym/portage_file.pyo
>>> /usr/lib/portage/pym/portage_util.py
>>> /usr/lib/portage/pym/getbinpkg.pyo
--- /usr/sbin/
>>> /usr/sbin/fixpackages -> ../lib/portage/bin/fixpackages
>>> /usr/sbin/env-update -> ../lib/portage/bin/env-update
>>> /usr/sbin/etc-update -> ../lib/portage/bin/etc-update
>>> /usr/sbin/emerge-webrsync -> ../lib/portage/bin/emerge-webrsync
>>> /usr/sbin/regenworld -> ../lib/portage/bin/regenworld
>>> /usr/sbin/archive-conf -> ../lib/portage/bin/archive-conf
>>> /usr/sbin/ebuild -> ../lib/portage/bin/ebuild
>>> /usr/sbin/dispatch-conf -> ../lib/portage/bin/dispatch-conf
>>> /usr/sbin/quickpkg -> ../lib/portage/bin/quickpkg
--- /usr/share/
--- /usr/share/doc/
--- /usr/share/doc/portage-2.0.51.22-r2/
>>> /usr/share/doc/portage-2.0.51.22-r2/ChangeLog.gz
--- /usr/share/man/
--- /usr/share/man/man1/
>>> /usr/share/man/man1/ebuild.1.gz
>>> /usr/share/man/man1/repoman.1.gz
>>> /usr/share/man/man1/etc-update.1.gz
>>> /usr/share/man/man1/emerge.1.gz
>>> /usr/share/man/man1/quickpkg.1.gz
>>> /usr/share/man/man1/env-update.1.gz
>>> /usr/share/man/man1/dispatch-conf.1.gz
--- /usr/share/man/man5/
>>> /usr/share/man/man5/ebuild.5.gz
>>> /usr/share/man/man5/portage.5.gz
>>> /usr/share/man/man5/make.conf.5.gz
>>> Safely unmerging already-installed instance...
--- !mtime obj /usr/share/man/man5/portage.5.gz
--- !mtime obj /usr/share/man/man5/make.conf.5.gz
--- !mtime obj /usr/share/man/man5/ebuild.5.gz
--- !mtime obj /usr/share/man/man1/repoman.1.gz
--- !mtime obj /usr/share/man/man1/quickpkg.1.gz
--- !mtime obj /usr/share/man/man1/etc-update.1.gz
--- !mtime obj /usr/share/man/man1/env-update.1.gz
--- !mtime obj /usr/share/man/man1/emerge.1.gz
--- !mtime obj /usr/share/man/man1/ebuild.1.gz
--- !mtime obj /usr/share/man/man1/dispatch-conf.1.gz
--- !mtime obj /usr/share/doc/portage-2.0.51.22-r2/ChangeLog.gz
--- !mtime obj /usr/lib/portage/pym/xpak.pyo
--- !mtime obj /usr/lib/portage/pym/xpak.py
--- !mtime obj /usr/lib/portage/pym/portage_util.pyo
--- !mtime obj /usr/lib/portage/pym/portage_util.py
--- !mtime obj /usr/lib/portage/pym/portage_locks.pyo
--- !mtime obj /usr/lib/portage/pym/portage_locks.py
--- !mtime obj /usr/lib/portage/pym/portage_localization.pyo
--- !mtime obj /usr/lib/portage/pym/portage_localization.py
--- !mtime obj /usr/lib/portage/pym/portage_gpg.pyo
--- !mtime obj /usr/lib/portage/pym/portage_gpg.py
--- !mtime obj /usr/lib/portage/pym/portage_file.pyo
--- !mtime obj /usr/lib/portage/pym/portage_file.py
--- !mtime obj /usr/lib/portage/pym/portage_exec.pyo
--- !mtime obj /usr/lib/portage/pym/portage_exec.py
--- !mtime obj /usr/lib/portage/pym/portage_exception.pyo
--- !mtime obj /usr/lib/portage/pym/portage_exception.py
--- !mtime obj /usr/lib/portage/pym/portage_dep.pyo
--- !mtime obj /usr/lib/portage/pym/portage_dep.py
--- !mtime obj /usr/lib/portage/pym/portage_db_test.pyo
--- !mtime obj /usr/lib/portage/pym/portage_db_test.py
--- !mtime obj /usr/lib/portage/pym/portage_db_template.pyo
--- !mtime obj /usr/lib/portage/pym/portage_db_template.py
--- !mtime obj /usr/lib/portage/pym/portage_db_flat.pyo
--- !mtime obj /usr/lib/portage/pym/portage_db_flat.py
--- !mtime obj /usr/lib/portage/pym/portage_db_cpickle.pyo
--- !mtime obj /usr/lib/portage/pym/portage_db_cpickle.py
--- !mtime obj /usr/lib/portage/pym/portage_db_anydbm.pyo
--- !mtime obj /usr/lib/portage/pym/portage_db_anydbm.py
--- !mtime obj /usr/lib/portage/pym/portage_data.pyo
--- !mtime obj /usr/lib/portage/pym/portage_data.py
--- !mtime obj /usr/lib/portage/pym/portage_contents.pyo
--- !mtime obj /usr/lib/portage/pym/portage_contents.py
--- !mtime obj /usr/lib/portage/pym/portage_const.pyo
--- !mtime obj /usr/lib/portage/pym/portage_const.py
--- !mtime obj /usr/lib/portage/pym/portage_checksum.pyo
--- !mtime obj /usr/lib/portage/pym/portage_checksum.py
--- !mtime obj /usr/lib/portage/pym/portage.pyo
--- !mtime obj /usr/lib/portage/pym/portage.py.rej
--- !mtime obj /usr/lib/portage/pym/portage.py
--- !mtime obj /usr/lib/portage/pym/output.pyo
--- !mtime obj /usr/lib/portage/pym/output.py
--- !mtime obj /usr/lib/portage/pym/getbinpkg.pyo
--- !mtime obj /usr/lib/portage/pym/getbinpkg.py
--- !mtime obj /usr/lib/portage/pym/emergehelp.pyo
--- !mtime obj /usr/lib/portage/pym/emergehelp.py
--- !mtime obj /usr/lib/portage/pym/dispatch_conf.pyo
--- !mtime obj /usr/lib/portage/pym/dispatch_conf.py
--- !mtime obj /usr/lib/portage/pym/dcdialog.pyo
--- !mtime obj /usr/lib/portage/pym/dcdialog.py
--- !mtime obj /usr/lib/portage/pym/cvstree.pyo
--- !mtime obj /usr/lib/portage/pym/cvstree.py
--- !mtime obj /usr/lib/portage/bin/xpak
--- !mtime obj /usr/lib/portage/bin/tbz2tool
--- !mtime obj /usr/lib/portage/bin/repoman
--- !mtime obj /usr/lib/portage/bin/regenworld
--- !mtime obj /usr/lib/portage/bin/quickpkg
--- !mtime obj /usr/lib/portage/bin/prepstrip
--- !mtime obj /usr/lib/portage/bin/prepman
--- !mtime obj /usr/lib/portage/bin/preplib.so
--- !mtime obj /usr/lib/portage/bin/preplib
--- !mtime obj /usr/lib/portage/bin/prepinfo
--- !mtime obj /usr/lib/portage/bin/prepallstrip
--- !mtime obj /usr/lib/portage/bin/prepallman
--- !mtime obj /usr/lib/portage/bin/prepallinfo
--- !mtime obj /usr/lib/portage/bin/prepalldocs
--- !mtime obj /usr/lib/portage/bin/prepall
--- !mtime obj /usr/lib/portage/bin/portageq
--- !mtime obj /usr/lib/portage/bin/portage_gpg_update.sh
--- !mtime obj /usr/lib/portage/bin/pkgname
--- !mtime obj /usr/lib/portage/bin/pkgmerge.new
--- !mtime obj /usr/lib/portage/bin/pkgmerge
--- !mtime obj /usr/lib/portage/bin/pemerge.py
--- !mtime obj /usr/lib/portage/bin/newsbin
--- !mtime obj /usr/lib/portage/bin/newman
--- !mtime obj /usr/lib/portage/bin/newlib.so
--- !mtime obj /usr/lib/portage/bin/newlib.a
--- !mtime obj /usr/lib/portage/bin/newins
--- !mtime obj /usr/lib/portage/bin/newinitd
--- !mtime obj /usr/lib/portage/bin/newexe
--- !mtime obj /usr/lib/portage/bin/newenvd
--- !mtime obj /usr/lib/portage/bin/newdoc
--- !mtime obj /usr/lib/portage/bin/newconfd
--- !mtime obj /usr/lib/portage/bin/newbin
--- !mtime obj /usr/lib/portage/bin/mirror.py
--- !mtime obj /usr/lib/portage/bin/md5check.sh
--- !mtime obj /usr/lib/portage/bin/md5check.py
--- !mtime obj /usr/lib/portage/bin/fperms
--- !mtime obj /usr/lib/portage/bin/fowners
--- !mtime obj /usr/lib/portage/bin/fixpackages
--- !mtime obj /usr/lib/portage/bin/fixdbentries
--- !mtime obj /usr/lib/portage/bin/fix-db.py

--- !mtime obj /usr/lib/portage/bin/find-requires
--- !mtime obj /usr/lib/portage/bin/etc-update
--- !mtime obj /usr/lib/portage/bin/env-update.sh
--- !mtime obj /usr/lib/portage/bin/env-update
--- !mtime obj /usr/lib/portage/bin/emerge-webrsync
--- !mtime obj /usr/lib/portage/bin/emerge
--- !mtime obj /usr/lib/portage/bin/emake
--- !mtime obj /usr/lib/portage/bin/ebuild.sh
--- !mtime obj /usr/lib/portage/bin/ebuild
--- !mtime obj /usr/lib/portage/bin/dosym
--- !mtime obj /usr/lib/portage/bin/dosed
--- !mtime obj /usr/lib/portage/bin/dosbin
--- !mtime obj /usr/lib/portage/bin/dopython
--- !mtime obj /usr/lib/portage/bin/domo
--- !mtime obj /usr/lib/portage/bin/doman
--- !mtime obj /usr/lib/portage/bin/dolib.so
--- !mtime obj /usr/lib/portage/bin/dolib.a
--- !mtime obj /usr/lib/portage/bin/dolib
--- !mtime obj /usr/lib/portage/bin/dojar
--- !mtime obj /usr/lib/portage/bin/doins
--- !mtime obj /usr/lib/portage/bin/doinitd
--- !mtime obj /usr/lib/portage/bin/doinfo
--- !mtime obj /usr/lib/portage/bin/dohtml
--- !mtime obj /usr/lib/portage/bin/dohard
--- !mtime obj /usr/lib/portage/bin/doexe
--- !mtime obj /usr/lib/portage/bin/doenvd
--- !mtime obj /usr/lib/portage/bin/dodoc
--- !mtime obj /usr/lib/portage/bin/dodir
--- !mtime obj /usr/lib/portage/bin/doconfd
--- !mtime obj /usr/lib/portage/bin/dobin
--- !mtime obj /usr/lib/portage/bin/dispatch-conf
--- !mtime obj /usr/lib/portage/bin/clean_locks
--- !mtime obj /usr/lib/portage/bin/chkcontents
--- !mtime obj /usr/lib/portage/bin/archive-conf
--- cfgpro obj /etc/make.globals
--- cfgpro obj /etc/make.conf.example
--- cfgpro obj /etc/etc-update.conf
--- !mtime obj /etc/env.d/05portage.envd
--- cfgpro dir /etc/env.d
--- cfgpro obj /etc/dispatch-conf.conf
--- !empty dir /usr/share/man/man5
--- !empty dir /usr/share/man/man1
--- !empty dir /usr/share/man
--- !empty dir /usr/share/doc/portage-2.0.51.22-r2
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/sbin
--- !empty dir /usr/lib/portage/pym
--- !empty dir /usr/lib/portage/bin
--- !empty dir /usr/lib/portage
--- !empty dir /usr/lib
--- !empty dir /usr/bin
--- !empty dir /usr
--- !empty dir /etc
--- !targe sym /usr/sbin/regenworld
--- !targe sym /usr/sbin/quickpkg
--- !targe sym /usr/sbin/fixpackages
--- !targe sym /usr/sbin/etc-update
--- !targe sym /usr/sbin/env-update
--- !targe sym /usr/sbin/emerge-webrsync
--- !targe sym /usr/sbin/ebuild
--- !targe sym /usr/sbin/dispatch-conf
--- !targe sym /usr/sbin/archive-conf
--- !targe sym /usr/lib/portage/bin/donewins
--- !targe sym /usr/bin/xpak
--- !targe sym /usr/bin/tbz2tool
--- !targe sym /usr/bin/repoman
--- !targe sym /usr/bin/portageq
--- !targe sym /usr/bin/emerge
--- !targe sym /usr/bin/ebuild
>>> original instance of package unmerged safely.

 * Feature additions are noted in help and make.conf descriptions.

 * Update configs using 'etc-update' please. Maintaining current configs
 * for portage and other system packages is fairly important for the
 * continued health of your system.

 * NOTICE: There have been changes in the location of some internal files
 *         to better match the FHS. The changes do not directly affect users
 *         but please be advised that changing between versions of portage
 *         with and without these changes may introduce some inconsistencies
 *         in package data regarding 'world' and 'virtuals' (provides).

 *         /var/cache/edb/world has moved to /var/lib/portage/world

 *         /var/cache/edb/virtuals has been deprecated and is now calculated
 *         on demand. Strictly _USER_ modifications to virtuals may go into
 *         /etc/portage/profile/virtuals and will not be modified by portage.

 * You may run 'emerge metadata' to perform cache updates if you have
 * changed versions of portage. This will provide a fairly dramatic
 * speedup. Alternatively, you may 'emerge sync' if it has been more
 * than 30 minutes since your last sync.
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/portage-2.0.51.22-r2 merged.

>>> clean: No packages selected for removal.

>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.


 * GNU info directory index is up-to-date.

Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/sandbox-1.2.11 to /
>>> md5 files   ;-) sandbox-1.2.9.ebuild
>>> md5 files   ;-) sandbox-1.2.10.ebuild
>>> md5 files   ;-) sandbox-1.2.11.ebuild
>>> md5 files   ;-) files/digest-sandbox-1.2.9
>>> md5 files   ;-) files/sandbox-1.2.9-uclibc-getcwd.patch
>>> md5 files   ;-) files/digest-sandbox-1.2.10
>>> md5 files   ;-) files/digest-sandbox-1.2.11
>>> md5 files   ;-) files/sandbox-1.2.10-uclibc-getcwd.patch
>>> md5 src_uri ;-) sandbox-1.2.11.tar.bz2
>>> Unpacking source...
>>> Unpacking sandbox-1.2.11.tar.bz2 to /var/tmp/portage/sandbox-1.2.11/work
 * Unpacking sandbox for ABI=x86...
>>> Unpacking sandbox-1.2.11.tar.bz2 to /var/tmp/portage/sandbox-1.2.11/work
 * Unpacking sandbox for ABI=amd64...
>>> Source unpacked.
 * 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.11-amd64/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-1.2.11-amd64/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating sandbox-1.2.11-x86/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating sandbox-1.2.11-x86/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 --build=x86_64-pc-linux-gnu --libdir=/usr/lib32
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 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/sandbox-1.2.11/work/sandbox-1.2.11-x86/config.log

!!! ERROR: sys-apps/sandbox-1.2.11 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.

 * Upgrade failed updating portage.  No changes have been made to
 * your system by the upgrade process.

 * You may safely re-execute this upgrade script after correcting any
 * any problems to resume the upgrade process.

 * Please report the following error and any errors above if you file
 * a bug at http://bugs.gentoo.org
emerge sandbox failed
So, I'm now stuck at this point, where gcc is buggered, won't compile, the sandbox is buggered....won't compile, all the software I need for this system is buggered because it won't compile.......2005.0 is not just buggy, its unworkable.

Here are the current specs from gcc-3.4.3

Code: Select all

Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/specs
Configured with: /var/tmp/portage/gcc-3.4.3-r1/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 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/3.4.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/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++
Thread model: posix
gcc version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7)
and here is the 2004.3-2005.0upgrade.sh script (just in case something is not correct on my system).

Code: Select all

#!/bin/bash
# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/amd64/2005.0/scripts/2004.3-2005.0upgrade.sh,v 1.6 2005/07/20 19:53:40 eradicator Exp $

TMPDIR="$(portageq envvar PORTAGE_TMPDIR)"
PORTDIR="$(portageq envvar PORTDIR)"

# change to yes if you want to use DISTCC
if portageq envvar FEATURES | grep -q distcc ; then
	export USE_DISTCC="yes"
else
	export USE_DISTCC="no"
fi

#--- You shouldn't need to chane anything past this line ---

PORTAGE_REQ=">=sys-apps/portage-2.0.51-r9"
GCC_CONFIG_REQ=">=sys-devel/gcc-config-1.3.9"
DISTCC_REQ=">=sys-devel/distcc-2.18.3-r1"
EMUL_GLIBC_REQ=">=app-emulation/emul-linux-x86-glibc-2.3.4.20041102"
LINUX_HEADERS_REQ=">=sys-kernel/linux-headers-2.6.8.1-r3"

# When do we need to emerge sandbox instead of portage?
PORTAGE_NEEDSANDBOX=">sys-apps/portage-2.0.51.19"
SANDBOX_REQ="sys-apps/sandbox"

TMPDIR="${TMPDIR}/2005.0_upgrade"

if ! source /sbin/functions.sh ; then
	echo "$0: Failed to source /sbin/functions.sh" >&2
	exit 1
fi

mkdir -p ${TMPDIR} &> /dev/null
cd ${TMPDIR}

myDie() {
	if [[ -f step5 ]] ; then
		eerror "Upgrade failed in stage 6.  We were unable to unmerge the"
		eerror "emul-linux-x86-glibc package.  This is the last step of the upgrade process."
	elif [[ -f step4 ]] ; then
		eerror "Upgrade failed in stage 5.  This is the biggest step of the upgrade"
		eerror "process.  We were unable to build glibc for your system."
		eerror "Try running:"
		eerror "FEATURES=-sandbox emerge --oneshot sys-libs/glibc && touch ${TMPDIR}/step5"
	elif [[ -f step3 ]] ; then
		eerror "Upgrade failed in stage 4.  The upgrade script failed to change"
		eerror "your /etc/make.profile symlink to the 2005.0 profile.  Did"
		eerror "you intend to set PORTDIR to something other than ${PORTDIR}"
		eerror "in the upgrade script?  If so, set it and re-execute the script."
	elif [[ -f step2 ]] ; then
		eerror "Upgrade failed in stage 3.  Your multilib configuration is"
		eerror "probably broken, but 64bit applications will work fine while"
		eerror "you debug the problem.  If you wish to revert to a working"
		eerror "2004.3 multilib system, then delete /lib32 and /usr/lib32"
		eerror "and re-emerge your emul-* packages.  This process might also"
		eerror "fix whatever problem prevented the upgrade."
	elif [[ -f step1 ]] ; then
		eerror "Upgrade failed in stage 2.  You still have a fully functional"
		eerror "2004.3 system."
	elif [[ -f step0 ]] ; then
		eerror "Upgrade failed in stage 1.  You still have a fully functional"
		eerror "2004.3 system."
	else
		eerror "Upgrade failed updating portage.  No changes have been made to"
		eerror "your system by the upgrade process."
	fi

	echo
	ewarn "You may safely re-execute this upgrade script after correcting any"
	ewarn "any problems to resume the upgrade process."
	echo
	eerror "Please report the following error and any errors above if you file"
	eerror "a bug at http://bugs.gentoo.org"

	echo "${@}"
	exit 1
}

if [[ ! -f step0 ]]; then
	if [[ ( -d /lib32 && ! -L /lib32 ) || ( -d /usr/lib32 && ! -L /usr/lib32 ) ]] ; then
		eerror "It looks like you have /lib32 or /usr/lib32 directories already."
		eerror "Have you already begun a manual upgrade?  If so, pleasse revert your"
		eerror "changes and restart the script."
		exit 1
	fi

	if [[ -x /usr/bin/readlink ]] && /usr/bin/readlink /etc/make.profile | grep -q 2005 ; then
		eerror "Your /etc/make.profile symlink is not set to the 2004.3 profile.  This script"
		eerror "expects a 2004.3 environment to start the upgrade.  If you have started manually"
		eerror "upgrading your system, please revert the changes and start the script again."
		exit 1
	fi

	if [[ "$(gcc -m32 -print-multi-directory)" != "32" ]]; then
		eerror "Your compiler does not have multilib support. Pleasse switch to a multilib"
		eerror "enabled compiler with gcc-config.  If you don't have one on your system, you can"
		eerror "emerga a multilib gcc by executing the following line:"
		eerror "FEATURES=-sandbox USE=multilib emerge gcc"
		exit 1
	fi

	if [[ -f /proc/config.gz ]] ; then
		KERNEL_CONFIG="gunzip -dc /proc/config.gz"
	elif [[ -f /proc/config.bz2 ]] ; then
		KERNEL_CONFIG="bunzip2 -dc /proc/config.bz2"
	elif [[ -f /proc/config ]] ; then
		KERNEL_CONFIG="cat /proc/config"
	elif [[ -f /lib/modules/$(uname -r)/build/.config ]] ; then
		KERNEL_CONFIG="cat /lib/modules/$(uname -r)/build/.config"
	elif [[ -f /lib/modules/$(uname -r)/source/.config ]] ; then
		KERNEL_CONFIG="cat /lib/modules/$(uname -r)/source/.config"
	else
		ewarn "Can't find a config for the running kernel, so we're assuminig"
		ewarn "you correctly have CONFIG_IA32_EMULATION (support for 32bit"
		ewarn "applications) enabled."
		KERNEL_CONFIG="echo CONFIG_IA32_EMULATION=y"
	fi

	if ! eval ${KERNEL_CONFIG} | grep -q CONFIG_IA32_EMULATION=y ; then
		myDie "Running kernel does not have support for executing 32bit applications.  You need to enable CONFIG_IA32_EMULATION in your running kernel."
	fi

	# Always install portage since current might not be multilib friendly
	USE=multilib FEATURES=-sandbox emerge -v --oneshot ${PORTAGE_REQ} || \
		myDie "emerge portage failed"

	if portageq has_version / ${PORTAGE_NEEDSANDBOX} ; then \
		USE=multilib FEATURES=-sandbox emerge -v --oneshot ${SANDBOX_REQ} || \
		myDie "emerge sandbox failed"
	fi

	touch step0
fi

if [[ ! -f step1 ]]; then
	if ! portageq has_version / ${GCC_CONFIG_REQ} ; then \
		emerge -v --oneshot ${GCC_CONFIG_REQ} || \
		myDie "emerge gcc-config failed"
	fi

	if ! portageq has_version / ${EMUL_GLIBC_REQ} ; then \
		emerge -v --oneshot ${EMUL_GLIBC_REQ} || \
		myDie "emerge emul-glibc failed"
	fi

	if [[ "${USE_DISTCC}" == "yes" ]]; then
		if ! portageq has_version / ${DISTCC_REQ} ; then \
			emerge -v --oneshot ${DISTCC_REQ} || \
			myDie "emerge distcc failed"
		fi
	fi

	touch step1
fi

if [[ ! -f step2 ]]; then
	portageq has_version / linux26-headers && emerge unmerge linux26-headers
	if ! portageq has_version / ${LINUX_HEADERS_REQ} ; then \
			emerge -v --oneshot ${LINUX_HEADERS_REQ} || \
			myDie "emerge linux headers failed"
	fi
	
	if ! [[ -f /etc/env.d/04multilib ]]; then
		emerge -v --oneshot baselayout || myDie "emerge baselayout failed"
	fi
	
	if ! [[ -f /etc/env.d/04multilib ]]; then
		myDie "baselayout did not create /etc/env.d/04multilib as expected."
	fi
	
	env-update || myDie "env-update failed"

	echo "int main(){return 0;}" > ${TMPDIR}/32test.c
	if ! gcc -m32 ${TMPDIR}/32test.c -o ${TMPDIR}/32test >& ${TMPDIR}/32test.comp.log ; then
		myDie "Error compiling 32bit executable.  Please see ${TMPDIR}/32test.comp.log"
	fi

	if ! ${TMPDIR}/32test >& ${TMPDIR}/32test.exec.log ; then
		myDie "Error executing 32bit executable.  Please see ${TMPDIR}/32test.exec.log"
	fi

	touch step2
fi

if [[ ! -f step3 ]]; then
	[[ -L /lib32 ]] && rm /lib32 && mkdir /lib32
	[[ -L /usr/lib32 ]] && rm /usr/lib32 && mkdir /usr/lib32
	[[ -L /usr/X11R6/lib32 ]] && rm /usr/X11R6/lib32 && mkdir /usr/X11R6/lib32
	cp /emul/linux/x86/{usr/,}lib32/libsandbox.so* /usr/lib32 &> /dev/null
	[[ -f /usr/lib32/libsandbox.so ]] || myDie "Failed to copy over 32bit libsandbox."
	cp /emul/linux/x86/usr/lib32/libc.so /usr/lib32 || myDie "Failed to copy 32bit libc"
	cp /emul/linux/x86/usr/lib32/libpthread.so /usr/lib32 || myDie "Failed to copy 32bit libpthread."
	cp /emul/linux/x86/usr/lib32/*crt*.o /usr/lib32 || myDie "Failed to copy 32bit *crt*.o"
	[[ -d /emul/linux/x86/usr/lib32/nptl ]] && mkdir /usr/lib32/nptl
	[[ -d /emul/linux/x86/usr/lib32/nptl ]] && cp /emul/linux/x86/usr/lib32/nptl/libc.so /usr/lib32/nptl
	[[ -d /emul/linux/x86/usr/lib32/nptl ]] && cp /emul/linux/x86/usr/lib32/nptl/libpthread.so /usr/lib32/nptl
	env-update || myDie "env-update failed"

	touch step3
fi

if [[ ! -f step4 ]]; then
	if [[ -L /etc/make.profile ]] ; then
		rm /etc/make.profile || myDie "rm of old profile failed"
	fi

	ln -s ${PORTDIR}/profiles/default-linux/amd64/2005.0 /etc/make.profile || \
		myDie "link of new profile failed"
	touch step4
fi

if [[ ! -f step5 ]]; then
	emerge -v --oneshot glibc || myDie "emerge glibc failed"
	touch step5
fi

if [[ ! -f step6 ]] ; then
	rm -f /emul/linux/x86/usr/lib/libsandbox.* &> /dev/null
	emerge unmerge emul-linux-x86-glibc || myDie "emerge emul-glibc failed"
	touch step6
fi

echo "-------------------------------------------------------------------"
echo "Congratulations, you're almost finished updating to 2005.0.  Please"
echo "run 'emerge -upv system' followed by 'emerge -uv system' to finish."

rm -rf ${TMPDIR}
Now, if that's enough, just let me know. If not, tell me what else to include and we'll get this party started.

I've been struggling with this for this week, last week, everything was fine, and gcc-3.4.3 was working well, now nothing is compiling correctly, can't find the libraries unless they're explicitly 64-bit....tells me it can't create C executables...what's up with that?

Al
As Socrates once said "I drank what?"
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Thu Jul 28, 2005 5:59 am

OldTango wrote:the config log as always reads

Code: Select all

configure:2287: checking for C compiler default output file name
configure:2290: x86_64-pc-linux-gnu-gcc -O3 -march=k8 -pipe -fomit-frame-pointer -DSB_HAVE_64BIT_ARCH   conftest.c  >&5
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find /emul/linux/x86/lib/libc.so.6
Right. Like I said, you didn't complete the upgrade. You don't have a 2005.0 glibc installed. Please read the common problems section of the upgrade guide. Yes, for a while there it was not 100% accurate because a version bump to glibc was not accompanied by a bump to the emul-glibc, so people in ~amd64 needed to use the older glibc, but that is now corrected in the upgrade process, and the script has been revised to take that problem into account... again, the solution to your problem is in the upgrade guide, and provided in my earlier post.
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Thu Jul 28, 2005 6:04 am

Albert, 2005.0 isn't buggered... you're not even on 2005.0 yet... something is wrong with your emerge portage that has nothing to do with the profile. The only thing done by the script has been 'emerge portage' at that point. What's your emerge --info say?
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Thu Jul 28, 2005 6:18 am

Also, Albert, did you re-emerge emul-glibc after going back to 2004.3? What's the config.log say from the sandbox error? I'm more concerned with the portage problem at this point, though as I haven't seen something like that...

And could you upen a bug report for the portage bug. Please provide the output of 'emerge --info' and 'emerge -d portage'
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Thu Jul 28, 2005 6:40 am

OldTango wrote:it appears not be able to locate /emul/linux/x86/lib/libc.so.6 which on my system is located /emul/linux/x86/lib/lib32 where the lib32 is a symlink pointing back to /emul/linux/x86/lib/. Inside /emul/linux/x86/lib/lib32 is libc.so.6, a symlink pointing to /emul/linux/x86/lib/lib32/libc-2.3.5.so
Ok wait a minute... I had to reread that like 5 times before I caught it... what the heck is /emul/linux/x86/lib/lib32 all about??? Did you really mean lib/lib32? That certainly isn't right. How did that happen? I'd recommend just deleting /emul and re-emerging the emul-* packages to have it setup right... probably some symlinking/portage bug or something messed up somewhere in the past...
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
Albert_Alligator
Apprentice
Apprentice
User avatar
Posts: 193
Joined: Wed May 12, 2004 3:09 pm
Location: Okefenokee Swamp
Contact:
Contact Albert_Alligator
Website

  • Quote

Post by Albert_Alligator » Thu Jul 28, 2005 9:45 am

Ok, so I went back through all of my steps, and this time I changed a few steps.

1. I have the 2005.0 Live CD and installed from there. I went to this page and followed the instructions, but didn't (much to your chagrin and my embarrassment) go to the Gentoo AMD64 Project Page before proceeding as advised. However, to be completely blunt, there is much information about a 64-bit install that should be a part of the installation.

For example:

Code: Select all

emerge app-emulation/emul-linux-x86-baselibs
emerge app-emulation/emul-linux-x86-xlibs
emerge app-emulation/emul-linux-x86-gtklibs
emerge app-emulation/emul-linux-x86-qtlibs
I had to emerge these that were found on the Gentoo/AMD64 Technotes Information section, which by the way isn't the place that this info should be kept if it is so nessecary to a working system, and when I mean working, I mean that most people using AMD64 systems are going to want to use programs that are 32-bit still, since not enough of the favorites are changed over, or through their buggy stage yet.

The reason I followed these directions;

Code: Select all

# rm -rf /lib32 /usr/lib32
# rm /etc/make.profile
# ln -s /usr/portage/profiles/default-linux/amd64/2004.3 /etc/make.profile
# emerge --sync
# emerge -v --oneshot '>=emul-linux-x86-glibc-2.3.4.20041102'
# rm -rf /var/tmp/2005.0_upgrade
# cd /usr/portage/profiles/default-linux/amd64/2005.0/scripts
# ./2004.3-2005.0upgrade.sh


was because my problem was mimicing the first guy who posted here, and the developer posted these instructions as a fix...actually, after I downloaded all the libs above, and added +nptlonly to my USE flags, the ./2004.3-2005.0upgrade.sh worked and set me back on my way.

My issue started on Monday, with a system that I installed just two weeks ago. The system worked ok up until Monday, when it started throwing out "can't find library" errors and stopping the compile.

When I said 2005.0 was buggered, I was saying it because its what I used to install my system....I took the latest portage image and the latest stage3 for AMD64 from the 2005.0 pages.

So, last week, emerge wasn't having problems....but Monday, after an emerge sync and emerge portage, my system was basically borked.

So now, after all that, I've emerged -uv system and it worked...including emerging gcc-3.4.4.

If there is anything I can give that would help developers understand what I did, or what was wrong, let me know and I'll be glad to help.

Al
As Socrates once said "I drank what?"
Top
OldTango
l33t
l33t
User avatar
Posts: 739
Joined: Sat Feb 21, 2004 5:08 pm
Contact:
Contact OldTango
Website

  • Quote

Post by OldTango » Thu Jul 28, 2005 2:55 pm

eradicator wrote
Ok wait a minute... I had to reread that like 5 times before I caught it... what the heck is /emul/linux/x86/lib/lib32 all about??? Did you really mean lib/lib32? That certainly isn't right. How did that happen? I'd recommend just deleting /emul and re-emerging the emul-* packages to have it setup right... probably some symlinking/portage bug or something messed up somewhere in the past...
Tango wrote
How confusing is this.........................................:lol:
Thanks so much for taking the time to read this post. I have been going crazy the last few weeks trying to figure this one out. I had suspected that there was something wrong with the /emul dir libs after reading many forum posts and bug reports on gcc, glibc, and other ererge errors. The fixes involved deleting certian libs or symlinks only and I had reservations on doing that.

So it appears that the many times I had gone back to the 2004.3 profile following the quide and common problems section and then upgradingw, was never going to slove my problem. Somewhere along the lines the /emul-* had been broked. I also suspect a portage bug when it comes to removing old stale links or libs.

After a

Code: Select all

rm -rf /emul*
and then re-emergeing the emul-linux-x86 libs that my system uses. I emerged sandbox error free and then for kicks I recompiled glibc. Glibc seemed to be having problems using my locales.build and userlocales use flag, but not today...............:D I dought this is related.

I have another post on the forums I am going to update about this same subject.

Thanks so much
Top
crazycat
l33t
l33t
User avatar
Posts: 838
Joined: Tue Aug 26, 2003 6:04 pm
Location: Hamburg, Germany

  • Quote

Post by crazycat » Thu Jul 28, 2005 3:07 pm

/emul stuff is gentoo madness, there are even more hidden 32bit libs like /usr/lib/gcc/blablabla/32. I mean why didn't one put 32bit libs in /usr/lib32 or /lib32, there is already part of it there. I mean each time i install some 32bit software i have to include several lines with cflags and ldflags and whatever before it. Hell some software refuses to work on this setup untill i copy the libs manually. Even then if i leave libs in /usr/lib32 gentoo gets so screwed that it is no longer possible to compile for example wine. Imagine something like emerge32 mplayer and u get 32bit mplayer with binaries in /usr/bin and libs in /usr/lib32. I mean there is a way that 32bit and 64bit can coexist peacfully like on fedora core. Why did getnoo decided to use emul stuff instead?
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Thu Jul 28, 2005 5:53 pm

Albert_Alligator wrote:

Code: Select all

emerge app-emulation/emul-linux-x86-baselibs
emerge app-emulation/emul-linux-x86-xlibs
emerge app-emulation/emul-linux-x86-gtklibs
emerge app-emulation/emul-linux-x86-qtlibs
I had to emerge these that were found on the Gentoo/AMD64 Technotes Information section, which by the way isn't the place that this info should be kept if it is so nessecary to a working system, and when I mean working, I mean that most people using AMD64 systems are going to want to use programs that are 32-bit still, since not enough of the favorites are changed over, or through their buggy stage yet.
All 32bit applications that need these have them as RDEPEND, so when you emerge the 32bit application (like openoffice-bin), they're brought in. What application did you emerge that didn't have these as dependencies? That's a bug
My issue started on Monday, with a system that I installed just two weeks ago. The system worked ok up until Monday, when it started throwing out "can't find library" errors and stopping the compile.
What library couldn't it find? If it can't find /emul/.../libc.so.6, then that's because you've got a 2004.3 emul-glibc on a 2005.0 system which is corrected using the upgrade script. But if you had 2005.0 from the beginning, then it would not be that library. What library couldn't it find?
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
Albert_Alligator
Apprentice
Apprentice
User avatar
Posts: 193
Joined: Wed May 12, 2004 3:09 pm
Location: Okefenokee Swamp
Contact:
Contact Albert_Alligator
Website

  • Quote

Post by Albert_Alligator » Fri Jul 29, 2005 10:40 am

eradicator wrote:All 32bit applications that need these have them as RDEPEND, so when you emerge the 32bit application (like openoffice-bin), they're brought in. What application did you emerge that didn't have these as dependencies? That's a bug
My issue started on Monday, with a system that I installed just two weeks ago. The system worked ok up until Monday, when it started throwing out "can't find library" errors and stopping the compile.
What library couldn't it find? If it can't find /emul/.../libc.so.6, then that's because you've got a 2004.3 emul-glibc on a 2005.0 system which is corrected using the upgrade script. But if you had 2005.0 from the beginning, then it would not be that library. What library couldn't it find?
I wish I had kept some of the logs and messages that I had. I'm sorry now that I didn't. But don't worry, I'm going to use the same 2005.0 install disk I used for that install, and I'll use the same stage3 tar and same portage snapshot that I used for another installation, I'll write it up and post it here if it does the same thing.

Cheers,

Al
As Socrates once said "I drank what?"
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Fri Jul 29, 2005 3:06 pm

crazycat wrote:Imagine something like emerge32 mplayer and u get 32bit mplayer with binaries in /usr/bin and libs in /usr/lib32. I mean there is a way that 32bit and 64bit can coexist peacfully like on fedora core. Why did getnoo decided to use emul stuff instead?
That's the goal. That's what we want to do, but portage doesn't support that yet. They coexist "peacefully" on fedora because fedora is a binary distribution. Gentoo policy is that /usr is populated by portage compiled binaries, and /opt (and /emul) are used for binary packages. If you want to help your 'emerge32 mplayer' a reality, then by all means, you're more than welcome to help out with the effort. Check this out.
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
crazycat
l33t
l33t
User avatar
Posts: 838
Joined: Tue Aug 26, 2003 6:04 pm
Location: Hamburg, Germany

  • Quote

Post by crazycat » Fri Jul 29, 2005 5:37 pm

There are some interesting thoughts in that email like binary/library dependencies. But i don't really know what .la files are nor do I know difference between CHOST and CHOST_ABI. I have learned c/c++ myself and lack this whole academical background. I can write a program which does specific things but i dont really know much about the rest like how system is configured. But i think that keepeng it simple is the best way even if it limits functionality in some degree. I am also don't know python very good so i dont really know how i could help in enchanting portage.
Top
eradicator
Retired Dev
Retired Dev
Posts: 144
Joined: Tue Apr 01, 2003 6:52 pm
Location: Berkeley, CA

  • Quote

Post by eradicator » Fri Jul 29, 2005 10:50 pm

Well, atleast you looked over it to see if you could help. That's appreciated. The 'keeping it simple' is what we have with the 'you emerge things in 64bit' now. The next step is to get support into the backend so we can manage installing 32bit and 64bit packages side by side through portage.
Gentoo Developer: amd64, sparc, sound, toolchain, accessibility
Top
Locked
18 posts • Page 1 of 1

Return to “Gentoo on AMD64”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy