Re: [gentoo-hardened] hardened_gcc_glibc2.3.3_nptl_headers2.6_bug53616

[Rumen Yotov]

On пн, 2004-06-21 at 23:24, Dennis Freise wrote:
> On Mon, 21 Jun 2004 23:12:18 +0300
> Rumen Yotov <rumen_yotov@×××.bg> wrote:
>
> > Wish to test the patch, but wanna ask what's the best way to do it?
> > First emerge ............linux-headers-2.6.3 for example.
> > Then ebuild ...glibc.. clean; ebuild ...glibc.. unpack;
> > Apply the patch; (cd /var/portage/tmp/work/glibc../; patch -p1 < patch)
> > later ebuild ....glibc... compile ebuild ..glibc.. install etc.
> > Or there are some already patched glibc-2.3.3-20040420.ebuild with the
> > patch included? Seems the second way is easier.
>
> You can include that patch in the ebuild yourself, it's very easy:
>
> edit /usr/portage/sys-libs/glibc/glibc-2.3.3.20040420.ebuild
>
> find line:
> cd ${S}; epatch ${FILESDIR}/2.3.2/${LOCAL_P}/iconvconfig-name_insert.patch
>
> insert _after_:
> cd ${S}; epatch ${FILESDIR}/2.3.4/${PN}-2.3.4-hardened-sysdep-shared.patch
>
> save
> add 'nptl' to your USE
> your gcc should be compiled with 'hardened' by now
> 'emerge --oneshot glibc'
>
> Done :-) Note that this change will be undone on next rsync, so you shouldn't
> recompile this particular glibc-version after another sync (until the patch gets
> applied you'll end up with the mentioned compile-error...).
>
> I'm not really sure if it's the best location for this patch in the ebuild, but
> it applied fine and glibc compiles fine. It's just for testing, so don't throw
> rocks at me ;)
Hi Dennis,
First thanks for the help. Put the glibc-20040420.ebuild in OVERLAY dir
and edited it accordingly. So i won't have to patch it again.
emerged linux-headers-2.6.4 and now i'm compiling glibc and as the time
passes it seems it'll be OK. Write this now as maybe when emerge ends
i'll have to re-emerge evolution with this ML-thread so i'm doing it
now. Evo requires a lot of time. Same for apache2. Think so because
re-emerged them when went to glibc w/o NPTL & 2.6 headers.
When emergeing glibc ends i'll post a report on BUG-52254 as success
(lets hope) or failure.
Rumen