From: Marc Giger <gigerstyle@gmx.ch>
To: gentoo-alpha@gentoo.org
Subject: Re: [gentoo-alpha] glibc blew up...
Date: Mon, 6 Oct 2003 09:08:50 +0200 [thread overview]
Message-ID: <20031006090850.43c8dc3e.gigerstyle@gmx.ch> (raw)
In-Reply-To: <20031006060729.GA21190@coruscant>
On Mon, 6 Oct 2003 08:07:29 +0200
Mathieu MILLET <htam@coruscant.interne.net> wrote:
> On Mon, Oct 06, 2003 at 12:05:18AM -0400,
> jwsacksteder@ramprecision.com wrote:
> > After 3 hours of chewing on the bootstrap script, glibc produced
> > the following message. If you have successfully built
> > glibc-2.3.2-r1, please let me know.
> [snip]
> >
>
> glibc-2.3.2-r1 is broken on alpha. You need a patch that has already
> been integrated in glibc-2.3.2-r6 (well maybe before, but I'm sure for
> this one).
>
> BUT 2.3.2-r6 has another problem and yet can't be compiled
> too (I have already submitted the bug for 2.3.2-r6, cf. bug#30302).
Yeah, I tried to build a cross-compiler for alpha on intel and came to
the same error. I thought it was a error which happens only when I build
a crosscompiler, it seems it isn't the case...
I asked myself (and now you) if it would be good if we place a new
ebuild in the portage tree WITH the latest CVS version of glibc. It has
a lot of fixes for alphas!?!
greets
Marc
--
gentoo-alpha@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-06 7:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 4:05 [gentoo-alpha] glibc blew up jwsacksteder
2003-10-06 6:07 ` Mathieu MILLET
2003-10-06 7:08 ` Marc Giger [this message]
2003-10-08 1:09 ` Aron Griffis
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 11:51 jwsacksteder
2003-10-06 18:17 ` Mathieu MILLET
2003-10-08 1:10 ` Aron Griffis
2003-10-08 1:58 jwsacksteder
2003-10-08 2:43 ` Aron Griffis
2003-10-08 3:23 jwsacksteder
2003-10-08 3:24 ` Aron Griffis
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=20031006090850.43c8dc3e.gigerstyle@gmx.ch \
--to=gigerstyle@gmx.ch \
--cc=gentoo-alpha@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