From: Zac Medico <zmedico@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge error with glibc and nptl
Date: Thu, 14 Jul 2005 12:12:45 -0700 [thread overview]
Message-ID: <42D6B92D.1090700@gmail.com> (raw)
In-Reply-To: <dff3752705071411516ea3c4d3@mail.gmail.com>
kristina clair wrote:
>
> Hm!
> CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer"
> CHOST="i386-pc-linux-gnu"
>
> I did not set this box up, so I'm not sure - is there any reason why
> someone would set the CHOST to that?
>
> I checked the /var/tmp/portage/glibc-2.3.4.20041102-r1/work directory,
> and indeed there is no subdirectory
> build-default-i386-pc-linux-gnu-nptl. In fact, in the work directory,
> there is only glibc-2.3.3.
>
> Thanks,
> Kristina
>
Well, i386-pc-linux-gnu is the generic CHOST for the x86 arch so it could be for a number of reasons. Maybe it was just a mistake. You might be able to change the CHOST and "emerge -e world" but the normally recommended solution is to reinstall with a stage3 for your chosen subarch.
Zac
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-07-14 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 18:04 [gentoo-user] emerge error with glibc and nptl kristina clair
2005-07-14 18:42 ` Zac Medico
2005-07-14 18:51 ` kristina clair
2005-07-14 19:12 ` Zac Medico [this message]
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=42D6B92D.1090700@gmail.com \
--to=zmedico@gmail.com \
--cc=gentoo-user@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