[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-amd64
Subject:    [gentoo-amd64] Re: Does gcc-3.4 do nptl?
From:       Duncan <1i5t5.duncan () cox ! net>
Date:       2004-06-30 7:00:39
Message-ID: pan.2004.06.30.07.00.39.28847 () cox ! net
[Download RAW message or body]

Travis Tilley posted <200406211058.57883.lv@gentoo.org>, excerpted below, 
on Mon, 21 Jun 2004 10:58:57 -0400:

> On Monday 21 June 2004 11:06 am, Duncan wrote:
>> I just tried switching profiles and emerging the newly stable gcc-3.4.
>> However, upon attempting to emerge glibc after that, it says my gcc
>> doesn't handle threading, to install something newer than 3.2.something,
>> which 3.4 obviously is..
> 
> 3.4 supports __thread... odd. what ebuild are you using? for glibc and gcc.
> 
>> (The other problem could be the glibc ebuild, which is package.masked, it
>> says, because it requires linux-headers-2.6 which are -* keyword masked,
>> but which I have installed for nptl anyway, and it says it's OK to unmask
>> when the headers are unmasked, implying it should be safe if they are
>> installed..)
> 
> when was the last time you did an emerge sync? 

I emerge sync b4 I do any new merges, which is basically any time I've
booted to Gentoo still, since I now have kdebase installed, but still not
the rest of the X stuff I routinely used on Mandrake.  (I haven't real
recently, as I've been to busy to do anything with Gentoo for a few days,
but I had immediately prior to emerging gcc 3.4 and the new glibcs.)

The problem was simply the new __thread test in the masked glibc ebuilds
(20040605-r1 and above). When folks said it worked (with unmasked), I
investigated a bit further and figured it out. 

I wouldn't have posted the question without trying the unmasked versions,
except I thought I'd seen something to the effect that it didn't work
somewhere and was attempting to confirm it one way or the other. Seems my
memory was faulty.  <g>  Once I confirmed that, I went back to
investigating, and found the problem right away.

So, it seems the linux-headers-2.6 issue isn't the ONLY reason they were
masked, at least for AMD64.  As I said, I haven't had time to do much
the last few days, however, the reason I haven't replied to this,
either, so the issue may be fixed by now.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin



--
gentoo-amd64@gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]