From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Glibc error while bootstrapping
Date: Wed, 19 Dec 2001 13:07:49 -0600 [thread overview]
Message-ID: <20011219130749.A10832@chiba.3jane.net> (raw)
In-Reply-To: <1008787281.21452.745.camel@nosferatu.lan>
On Wed, Dec 19, 2001 at 08:41:18PM +0200, Martin Schlemmer wrote:
> No expert in the bootstrap phase, but if you look at:
>
> Illegal instruction
> make[2]: *** Waiting for unfinished jobs....
>
> ,my guess is that there is some i686 code still somewhere
> in the build iso/image (as Verwilst have a k6-2 ..).
This could also easily be caused by using the wrong CFLAGS (-march=i686
would do it) on a K6-class system.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-12-19 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 14:38 [gentoo-dev] Glibc error while bootstrapping Bart Verwilst
2001-12-19 15:19 ` Daniel Robbins
2001-12-19 18:41 ` Martin Schlemmer
2001-12-19 19:07 ` Daniel Robbins [this message]
2001-12-20 1:12 ` Bart Verwilst
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=20011219130749.A10832@chiba.3jane.net \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@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