public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Donahue <donahue95@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Problems customizing gentoo
Date: Thu, 02 Oct 2008 21:56:58 -0400	[thread overview]
Message-ID: <1222999018.1002.2.camel@oddman.donahues.us.> (raw)
In-Reply-To: <200810021942.45089.rick@aofh.us>

On Thu, 2008-10-02 at 19:42 -0500, Rick Meredith wrote:
> On Thursday 02 October 2008 04:35:03 pm Greg wrote:
> > I've been having problems customizing gentoo on my Acer Aspire T180-UA380B
> > AMD Desktop PC.
> >
> > I've been using i686 versions of gentoo for years on my pentium3 with no
> > problems.
> >
> > Here are further specs and what I've tried:
> >
> >    Acer Aspire T180-UA380B AMD Desktop PC - AMD Athlon 64
> >    3800+ 2.4GHz, 2GB DDR2, 160GB SATA, DL DVD±RW, Gigabit LAN, Flash
> >    Reader, running off of a 2007.0 AMD64 live cd chrooted environment.
> >
> > I keep running into the same issue no matter what USE flags I have
> > specified in make.conf, what make.profile I have specified (attempted
> > 2007.0, 2008.0, hardened, 2007.0 x86 under a 32bit chrooted environment and
> > chost set accordingly in make.conf.
> >
> > The error I get follows:
> >  * ERROR: sys-libs/glibc-2.6.1 failed.
> >  * Call stack:
> >  * ebuild.sh, line 49:  Called src_compile
> >  * environment, line 3362:  Called eblit-run 'src_compile'
> >  * environment, line 1087:  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 default 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:20081002-111002.log'. * The ebuild
> > environment file is located at
> > '/var/build/portage/sys-libs/glibc-2.6.1/temp/environment'. *
> >
> > If I start off with a stage3-amd64-2007.0 tarvol, don't try to customize my
> > system by trying to make a stage1, and just do emerge --update system, I
> > end up with errors upgrading grep regarding libpcre.
> >
> > Anythoughts would be greatly appreciated as I've been struggling with this
> > for months trying to find a solution.
> >
> > If I need to provide more information or need to post this to a more
> > appropriate list, please let me know.
> >
> > Very best,
> > Greg Osborne
> 
> What do you have in your "/etc/make.conf"
> 
> Regards Rick
> 
TRY using 2008.0 minimal livecd following the handbook in detail as
though you were a gentoo first timer. A lot of knowledge is also a
dangerous thing.




  reply	other threads:[~2008-10-03  1:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 21:35 [gentoo-amd64] Problems customizing gentoo Greg
2008-10-02 21:53 ` Tonko Mulder
2008-10-03  0:42 ` Rick Meredith
2008-10-03  1:56   ` Drake Donahue [this message]
     [not found]   ` <19351.0605059148$1222999100@news.gmane.org>
2008-10-03  9:08     ` [gentoo-amd64] " Duncan
2008-10-03  7:50 ` [gentoo-amd64] " Beso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1222999018.1002.2.camel@oddman.donahues.us. \
    --to=donahue95@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox