1 |
On Mon, 2004-06-21 at 13:55, Dennis Freise wrote: |
2 |
> On Mon, 21 Jun 2004 20:47:55 +0300 |
3 |
> Rumen Yotov <rumen_yotov@×××.bg> wrote: |
4 |
> |
5 |
> > > That's a dupe of #52254. Look over there. Patch is there, I tested it and it |
6 |
> > > compiles fine, but it's not yet in portage on any not-masked ebuilds. If you |
7 |
> > > want a hardened-gcc + glibc/nptl I would recommend waiting a little longer |
8 |
> > > until that patch gets applied to glibc-2.3.3.20040420, or any newer glibc |
9 |
> > > gets unmasked. |
10 |
> > > |
11 |
> > Using all ~x86 system. |
12 |
> > At the moment did 'emerge glibc-2.3.3-20040420 -f' and it also fetched: |
13 |
> > glibc-2.3.3-branch-update-20040420.patch.bz2 (already had: |
14 |
> > glibc-linuxthreads-2.3.2.tar.bz2). But i'll wait not in a hurry ;-) |
15 |
> |
16 |
> That branch-update is the reason why it's called glibc-*2.3.3-20040420* :-) |
17 |
> Nothing new in that update, it was always there. In my portage (synced this am |
18 |
> @ 3:25) the glibc-ebuild didn't contain the hardened-sysdep-shared patch, so it |
19 |
> won't compile with USE="hardened nptl". You could apply that patch yourself |
20 |
> though... |
21 |
> |
22 |
> > > > Still no solution for mysql-4.0.20? |
23 |
> > > |
24 |
> > > What do you mean ? I compiled mysql-4.0.20 with a hardened-gcc just |
25 |
> > > yesterday - no problems. |
26 |
> > I mean that in BUG-53616 mysql-4.0.20 is also pointed as blocker for |
27 |
> > this bug. |
28 |
> |
29 |
> Well, for your convinience, I just tried it again, using hardened-gcc -3.3.3-r6, |
30 |
> glibc/+nptl and linux-headers-2.6.6 - it compiled fine. I can't confirm that |
31 |
> bug. |
32 |
|
33 |
|
34 |
Just a note for everybody.. |
35 |
That patch will not be added till a few people confirm it solves the |
36 |
problem for them on that bug (ie not mailing lists). |
37 |
|
38 |
-- |
39 |
Ned Ludd <solar@g.o> |
40 |
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |