public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: Davide Cittaro <davide.cittaro@ifom-ieo-campus.it>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] glibc 2.5+
Date: Mon, 28 May 2007 17:11:56 +0200	[thread overview]
Message-ID: <680EC22B-0F89-4161-9FC9-8DFC492C4718@ifom-ieo-campus.it> (raw)
In-Reply-To: <20070528150610.GK22162@woodpecker.gentoo.org>

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


On May 28, 2007, at 5:06 PM, Bryan Østergaard wrote:

> On Mon, May 28, 2007 at 04:01:15PM +0200, Davide Cittaro wrote:
>> Hi all, I've found that glibc 2.5+ cannot be compiled on my alpha, as
>> reported on gentoo bugzilla by another person.
>>
>> http://bugs.gentoo.org/show_bug.cgi?id=179353
>>
>> I have a couple of questions, then:
>> 1- it is safe to use '-nptlonly' flag?
> Not really. In the past we've found Linuxthreads to be unstable and
> nptlonly is much preferred for that reason (we had programs randomly
> crashing with Linuxthreads and no problems with NPTL).
>

After 1 hour of building I've discovered that glibc doesn't compile  
even without nptlonly flag

>> 2- when the patched glibc will be available in portage (comment 2 of
>> that bug has been posted  one week ago)?
> As soon as glibc upstream fixes the problem. Meanwhile you have two
> different options.
>
> 1. Upgrade to binutils >=2.17.50.0.15 and risk possible unknown bugs
> from doing so.
> 2. Ignoring glibc-2.5 updates until upstream fixes the issue.
>
> My recommendation would be to wait and not try to work around the  
> issue
> yourself.

Unfortunately I have strict times and this general system update has  
been scheduled for this week. Since glibc-2.5-r2 is marked stable on  
alpha I thought I wouldn't run into such issues... :-(
If I upgrade binutils can I use both nptl* flags?

d

/*
Davide Cittaro
HPC and Bioinformatics Systems @ Informatics Core

IFOM - Istituto FIRC di Oncologia Molecolare
via adamello, 16
20139 Milano
Italy

tel.: +39(02)574303007
e-mail: davide.cittaro@ifom-ieo-campus.it
*/



[-- Attachment #2: Type: text/html, Size: 7700 bytes --]

  reply	other threads:[~2007-05-28 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 14:01 [gentoo-alpha] glibc 2.5+ Davide Cittaro
2007-05-28 15:06 ` Bryan Østergaard
2007-05-28 15:11   ` Davide Cittaro [this message]
2007-05-28 15:49     ` Bryan Østergaard
2007-06-01  9:49       ` Davide Cittaro

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=680EC22B-0F89-4161-9FC9-8DFC492C4718@ifom-ieo-campus.it \
    --to=davide.cittaro@ifom-ieo-campus.it \
    --cc=gentoo-alpha@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