* Did not find "selinux" in use, building with GRSec2 support. * Dropping *lsm*... * Dropping 20_selinux-newapi-2.4.22.patch... * Dropping 24_selinux-pax-linux-2.4.22-200309012325.patch... * Dropping 26_selinux-pax+obs-linux-2.4.22-200308302223.patch... * Dropping 30_selinux-dm1-2.4.22.patch... * Dropping 32_selinux-evms-2.1.1.patch... * Dropping 40_selinux-systrace-v1.4-2.4.22.patch... * Dropping 50_selinux-superfreeswan-1.99.8-v2.4.22.patch... * Dropping 60_selinux-propolice.patch... * Applying do_brk_fix.patch... * Failed Patch: do_brk_fix.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/hardened-sources-2.4.22/temp/do_brk_fix.patch-8543.out !!! ERROR: sys-kernel/hardened-sources-2.4.22 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: do_brk_fix.patch! Reproducible: Always Steps to Reproduce: 1.cd /usr/portage/sys-kernel 2.emerge hardened-sources-2.4.22.ebuild 3.
ditto, me to, patch fails, emerge fails... I checked the file mm/mmap.c and it certianly has not had the patch applied.
If I add cd ${S} before the epatch line in the ebuild the emerge works doing emerge sync erases the changes to the ebuild tho.
*** Bug 39056 has been marked as a duplicate of this bug. ***
can you add a diff what you did to the hardened-sources? thanks in advance. also be sure to look at the patch which failed, because the error message is kind of problematic: it says "Failed Patch: xxx" but the real failed patch causing this can be one of the patches before that one mentioned to have failed. sincerely, Alex
Please upgrade to hardened-sources-2.4.24-r1
