| 1 |
On Mon, 21 Jun 2004 20:47:55 +0300 |
| 2 |
Rumen Yotov <rumen_yotov@×××.bg> wrote: |
| 3 |
|
| 4 |
> > That's a dupe of #52254. Look over there. Patch is there, I tested it and it |
| 5 |
> > compiles fine, but it's not yet in portage on any not-masked ebuilds. If you |
| 6 |
> > want a hardened-gcc + glibc/nptl I would recommend waiting a little longer |
| 7 |
> > until that patch gets applied to glibc-2.3.3.20040420, or any newer glibc |
| 8 |
> > gets unmasked. |
| 9 |
> > |
| 10 |
> Using all ~x86 system. |
| 11 |
> At the moment did 'emerge glibc-2.3.3-20040420 -f' and it also fetched: |
| 12 |
> glibc-2.3.3-branch-update-20040420.patch.bz2 (already had: |
| 13 |
> glibc-linuxthreads-2.3.2.tar.bz2). But i'll wait not in a hurry ;-) |
| 14 |
|
| 15 |
That branch-update is the reason why it's called glibc-*2.3.3-20040420* :-) |
| 16 |
Nothing new in that update, it was always there. In my portage (synced this am |
| 17 |
@ 3:25) the glibc-ebuild didn't contain the hardened-sysdep-shared patch, so it |
| 18 |
won't compile with USE="hardened nptl". You could apply that patch yourself |
| 19 |
though... |
| 20 |
|
| 21 |
> > > Still no solution for mysql-4.0.20? |
| 22 |
> > |
| 23 |
> > What do you mean ? I compiled mysql-4.0.20 with a hardened-gcc just |
| 24 |
> > yesterday - no problems. |
| 25 |
> I mean that in BUG-53616 mysql-4.0.20 is also pointed as blocker for |
| 26 |
> this bug. |
| 27 |
|
| 28 |
Well, for your convinience, I just tried it again, using hardened-gcc -3.3.3-r6, |
| 29 |
glibc/+nptl and linux-headers-2.6.6 - it compiled fine. I can't confirm that |
| 30 |
bug. |
| 31 |
|
| 32 |
-- |
| 33 |
Dennis Freise <cat@××××××××××××××××××.cx> |
| 34 |
GnuPG key: 2DE8 CCEF 6E20 11D4 3B27 21EC B0BA 1749 D2C8 38ED |
| 35 |
Available at: http://www.final-frontier.ath.cx/?key-plain |
Archives