| 1 |
On Mon, 21 Jun 2004 23:12:18 +0300 |
| 2 |
Rumen Yotov <rumen_yotov@×××.bg> wrote: |
| 3 |
|
| 4 |
> Wish to test the patch, but wanna ask what's the best way to do it? |
| 5 |
> First emerge ............linux-headers-2.6.3 for example. |
| 6 |
> Then ebuild ...glibc.. clean; ebuild ...glibc.. unpack; |
| 7 |
> Apply the patch; (cd /var/portage/tmp/work/glibc../; patch -p1 < patch) |
| 8 |
> later ebuild ....glibc... compile ebuild ..glibc.. install etc. |
| 9 |
> Or there are some already patched glibc-2.3.3-20040420.ebuild with the |
| 10 |
> patch included? Seems the second way is easier. |
| 11 |
|
| 12 |
You can include that patch in the ebuild yourself, it's very easy: |
| 13 |
|
| 14 |
edit /usr/portage/sys-libs/glibc/glibc-2.3.3.20040420.ebuild |
| 15 |
|
| 16 |
find line: |
| 17 |
cd ${S}; epatch ${FILESDIR}/2.3.2/${LOCAL_P}/iconvconfig-name_insert.patch |
| 18 |
|
| 19 |
insert _after_: |
| 20 |
cd ${S}; epatch ${FILESDIR}/2.3.4/${PN}-2.3.4-hardened-sysdep-shared.patch |
| 21 |
|
| 22 |
save |
| 23 |
add 'nptl' to your USE |
| 24 |
your gcc should be compiled with 'hardened' by now |
| 25 |
'emerge --oneshot glibc' |
| 26 |
|
| 27 |
Done :-) Note that this change will be undone on next rsync, so you shouldn't |
| 28 |
recompile this particular glibc-version after another sync (until the patch gets |
| 29 |
applied you'll end up with the mentioned compile-error...). |
| 30 |
|
| 31 |
I'm not really sure if it's the best location for this patch in the ebuild, but |
| 32 |
it applied fine and glibc compiles fine. It's just for testing, so don't throw |
| 33 |
rocks at me ;) |
| 34 |
|
| 35 |
-- |
| 36 |
Dennis Freise <cat@××××××××××××××××××.cx> |
| 37 |
GnuPG key: 2DE8 CCEF 6E20 11D4 3B27 21EC B0BA 1749 D2C8 38ED |
| 38 |
Available at: http://www.final-frontier.ath.cx/?key-plain |
Archives