Hi!
Started the installation of 64 bit gentoo yesterday (when I saw that 2005.0 was available)... everything went smooth, until I rebooted into my new shiny system.
The tar command keeps segfaulting on me when bootin directly into the system. The same binary works flawlessly when chrooting from the livecd into the system.
Running stable amd64 (with one exception see below)
* Tried running memtest86+ for 3 hours without any errors
* Tried kernel gentoo-sources-2.6.11-r4 (gentoo-sources-2.6.9-r14 seems a bit old?) but that didn't make tar work
* Re-emerged glibc and tar (both from amd64 stable), still non-working tar
* I haven't looked at the core file dumped by tar yet
Now to what I did find out:
* According to strace (strace dump attached) it seems like tar barely gets through loading some libs, bailing out when reaching yp stuff. Hmmm... I don't run ypbind when chrooting into the system from the livecd, but I do run it on the fully booted system. Might be something to investigate a bit more... Yep, turning off ypbind makes tar complete unpacking any tar-archive... strange... Re-emergeing ypbind doesn't help...
What might be the reason for this? I have run out of clues...
Here's my make.conf USE, CFLAGS and CHOST variables:
USE="-gtk -gnome -ipv6 alsa cdr dvd dvdr jack kde nptl ntplonly qt"
CFLAGS="-march=k8 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="x86_64-pc-linux-gnu"/Andreas
tar.strace.bz2
Description: Binary data
-- [email protected] mailing list
