Bootstrapping prefix Gentoo failed at an early stage for me on a SUSE Linux Enterprise Server 9.3 machine. I followed the September 11, 2007 version of http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml. The commands that I type in, as an unprivileged user, were: mkdir -p /tmp/local/g2 cd /tmp/local/g2 export EPREFIX=`pwd` export PATH="$EPREFIX/usr/bin:$EPREFIX/bin:$EPREFIX/tmp/usr/bin:$EPREFIX/tmp/bin:$PATH" wget http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/scripts/bootstrap-prefix.sh?format=txt chmod +x bootstrap-prefix.sh\?format\=txt mv bootstrap-prefix.sh\?format\=txt bootstrap-prefix.sh ./bootstrap-prefix.sh $EPREFIX tree ./bootstrap-prefix.sh $EPREFIX/tmp wget ./bootstrap-prefix.sh $EPREFIX/tmp python ./bootstrap-prefix.sh $EPREFIX portage export LDFLAGS="-L${EPREFIX}/usr/lib{64,} -Wl,-rpath=${EPREFIX}/usr/lib{64,} -L${EPREFIX}/lib{64,} -Wl,-rpath=${EPREFIX}/lib{64,}" export CPPFLAGS="-I${EPREFIX}/usr/include" hash -r emerge --oneshot sed Everything went fine up to the `emerge --oneshot sed' step. See attachments. The very last lines go: >>> Compiling source in /tmp/local/g2/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5 ... /bin/sed ./configure --prefix=/tmp/local/g2/usr --host=i686-pc-linux-gnu --mandir=/tmp/local/g2/usr/share/man --infodir=/tmp/local/g2/usr/share/info --datadir=/tmp/local/g2/usr/share --sysconfd ir=/tmp/local/g2/etc --localstatedir=/tmp/local/g2/var/lib --bindir=/tmp/local/g2/bin --disable-nls --build=i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-gcc... no checking for gcc... 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 following file when seeking support: !!! /tmp/local/g2/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5/config.log * * ERROR: sys-apps/sed-4.1.5 failed. * Call stack: * , line : Called die * The specific snippet of code: * * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/tmp/local/g2/var/tmp/portage/sys-apps/sed-4.1.5/temp/build.log'. * * Messages for package sys-apps/sed-4.1.5: * * ERROR: sys-apps/sed-4.1.5 failed. * Call stack: * , line : Called die * The specific snippet of code: * * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/tmp/local/g2/var/tmp/portage/sys-apps/sed-4.1.5/temp/build.log'.
Created attachment 134530 [details] console output entire console output, compressed with bzip2.
Created attachment 134531 [details] $EPREFIX/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5/config.log $EPREFIX/var/tmp/portage/sys-apps/sed-4.1.5/work/sed-4.1.5/config.log
This won't expand (bug in the howto): export LDFLAGS="-L${EPREFIX}/usr/lib{64,} -Wl,-rpath=${EPREFIX}/usr/lib{64,} -L${EPREFIX}/lib{64,} -Wl,-rpath=${EPREFIX}/lib{64,}" Please replace it by the properly expanded version (usr/lib64 usr/lib lib64 lib)
I noticed that the webpage is updated now; I am re-trying the new setting for LDFLAGS right now and all looks fine. Just a minor thing: I suppose the date of the webpage should be updated (it still says September 11).
ok, fixed the date in the doc now. Considering this one as fixed.
