public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-alpha@gentoo.org
Subject: Re: [gentoo-alpha] glibc blew up...
Date: Tue, 7 Oct 2003 21:09:19 -0400	[thread overview]
Message-ID: <20031008010919.GB17562@time> (raw)
In-Reply-To: <20031006060729.GA21190@coruscant>

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

Mathieu MILLET wrote:	[Mon Oct 06 2003, 02:07:29AM EDT]
> 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).

It's only broken with the latest gcc which adds some checks which
weren't there before.  I have glibc-2.3.2-r1 installed on my alpha and
was quite surprised when it wouldn't rebuild...! ;-)

> 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, it would be great to get the latest glibc on alpha.  Richard
Henderson has been doing a lot of work on it.

I'll see what I can do about 2.3.2-r6.

On a related note, anybody know what you have to do to make nptl work?
What breaks when you enable it?  Anything?

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-10-08  1:09 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
2003-10-08  1:09   ` Aron Griffis [this message]
  -- 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=20031008010919.GB17562@time \
    --to=agriffis@gentoo.org \
    --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