2008/10/3 Greg <[EMAIL PROTECTED]>:
> Thanks greatly for the responses. I have found them informative, but am sad 
> to report the same result.
>
> I downloaded and installed the stage3-amd64-2008.0 tarvol.
> after copying over a few configuration files to save myself time (mainly 
> /etc/make.conf, /etc/locale.gen, /etc/passwd,
> /etc/shadow, /etc/resolv.conf, and my ssh hostkeys)
> I then performed emerge -e world
>
> I ended up with the same kind of message:
>
>
>
>  * Messages for package sys-devel/gcc-4.1.2:
>
>  * If you have issues with packages unable to locate libstdc++.la,
>  * then try running 'fix_libtool_files.sh' on the old gcc versions.
>
>  * Messages for package sys-libs/glibc-2.6.1:
>
>  *
>  * ERROR: sys-libs/glibc-2.6.1 failed.
>  * Call stack:
>  * ebuild.sh, line 49:  Called src_compile
>  * environment, line 3431:  Called eblit-run 'src_compile'
>  * environment, line 1110:  Called eblit-glibc-src_compile
>  * src_compile.eblit, line 173:  Called src_compile
>  * environment, line 3431:  Called eblit-run 'src_compile'
>  * environment, line 1110:  Called eblit-glibc-src_compile
>  * src_compile.eblit, line 181:  Called toolchain-glibc_src_compile
>  * src_compile.eblit, line 122:  Called die
>  * The specific snippet of code:
>  * make PARALLELMFLAGS="${MAKEOPTS}" || die "make for ${ABI} failed"
>  * The die message:
>  * make for x86 failed
>  *
>  * If you need support, post the topmost build error, and the call stack if 
> relevant.
>  * A complete build log is located at 
> '/var/log/portage/sys-libs:glibc-2.6.1:20081003-103750.log'.
>  * The ebuild environment file is located at 
> '/var/build/portage/sys-libs/glibc-2.6.1/temp/environment'.
>  *
>
> Here is the copy of my make.conf file that I'm trying to use. I kept 
> make.profile as
> /usr/portage/profiles/default/linux/amd64/2008.0
> I always do env-update and source /etc/profile, so these haven't been the 
> issues.
>
> I knew stage1s were no longer supported, but I came into using gentoo back in 
> 2004 and learned how to use it through
> setting up stage1, making stage2, etc. I've never had major problems doing 
> that with the various versions until now. I
> wasn't sure if emerge -e system or emerge -e world etc would do the same 
> tasks.
>
> Anyways, here is my make.conf -- and again, thanks for all the help and 
> suggestions.
>
> CFLAGS="-march=nocona -O2 -pipe"

first of all: nocona breaks your build. nocona isn't an amd processor
but an emt64 (intel). for your processor you need to use march=k8.
also, i'd use -Os instead of -O2 since it has some speed and size
optimizations and it's stable. if you've recompiled gcc like that you
probably won't be able to compile other packages after that and need
to restart the stage-3. for fresh stage 3 go to www.funtoo.org and
download the one you want. don't delete the distfiles since you'll
probably need them again.

> CXXFLAGS="${CFLAGS} -fpermissive"

remove -fpermissive and set it as per package if it's needed.

> CHOST="x86_64-pc-linux-gnu"
> USE="3dnow mmx sse sse2 threads threadpool -multilib"

sse isn't supported on athlons, so remove it


> #ACCEPT_KEYWORDS="~amd64"

this should accept both amd64 and ~amd64

> PORTAGE_TMPDIR=/var/build
> PORTDIR=/usr/portage
> PKGDIR=${PORTDIR}/packages
> PORT_LOGDIR=/var/log/portage
> GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://adelie.polymtl.ca/ 
> http://distfiles.gentoo.org 
> http://www.ibiblio.org/pub/Linux/distributions/gentoo";
>
> SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
> PORTAGE_RSYNC_RETRIES="3"
> #EMERGE_DEFAULT_OPTS=""
> MAKEOPTS="-j3"

you could set this to -j5 without any issue. if you point the
/var/build directory to a /tmpfs (if you have some ram (about 3-4gb is
better, but if you don't have it, with at least 2gb you could try it
out)) you could also go with -j (unlimited jobs) or something near 8-9
jobs without killing the system.

> #PORTAGE_NICENESS=10
> AUTOCLEAN="yes"
> PORTAGE_TMPFS="/tmp"
> FEATURES="sandbox userpriv usersandbox notitles fixpackages loadpolicy 
> unmerge-orphans"

remove unmerge-orphans from the features while compiling for the first time.

-- 
dott. ing. beso

Reply via email to