I'm trying to build gentoo-2.4.19-r10 kernel. I did "emerge /usr/portage/sys-kernel/gentoo-sources/gentoo-sources-2.4.19-r10.ebuild" then, error "Failed Patch: do_brk_fix.patch!" and emerge failed. Reproducible: Always Steps to Reproduce: 1.emerge /usr/portage/sys-kernel/gentoo-sources/gentoo-sources-2.4.19-r10.ebuild 2. 3. Actual Results: console log: centralpark root # emerge /usr/portage/sys-kernel/gentoo-sources/gentoo-sources-2.4.19-r10.ebuild Calculating dependencies ...done! >>> emerge (1 of 1) sys-kernel/gentoo-sources-2.4.19-r10 to / >>> md5 src_uri ;-) linux-2.4.19.tar.bz2 >>> md5 src_uri ;-) patches-2.4.19-gentoo-r10.tar.bz2 >>> Unpacking source... >>> Unpacking linux-2.4.19.tar.bz2 to /var/tmp/portage/gentoo-sources-2.4.19-r10/work >>> Unpacking patches-2.4.19-gentoo-r10.tar.bz2 to /var/tmp/portage/gentoo-sources-2.4.19-r10/work patching file arch/i386/kernel/entry.S patching file drivers/char/drm/i810_dma.c patching file drivers/char/drm-4.0/i810_dma.c * Applying do_brk_fix.patch... * Failed Patch: do_brk_fix.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/gentoo-sources-2.4.19-r10/temp/do_brk_fix.patch-1995.out !!! ERROR: sys-kernel/gentoo-sources-2.4.19-r10 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: do_brk_fix.patch! centralpark root # Expected Results: I want that the same emerge succeed. Error message says "Include in your bugreport the contents of /var/tmp/portage/gentoo-sources-2.4.19-r10/temp/do_brk_fix.patch-2144.out" That is: -----------------------------------------------------------from here ***** do_brk_fix.patch ***** ============================ PATCH COMMAND: patch -p0 < /usr/portage/sys-kernel/gentoo-sources/files/do_brk _fix.patch ============================ can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/mm/mmap.c Fri Sep 12 06:44:06 2003 |+++ b/mm/mmap.c Thu Oct 2 01:18:19 2003 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p1 < /usr/portage/sys-kernel/gentoo-sources/files/do_brk _fix.patch ============================ can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/mm/mmap.c Fri Sep 12 06:44:06 2003 |+++ b/mm/mmap.c Thu Oct 2 01:18:19 2003 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p2 < /usr/portage/sys-kernel/gentoo-sources/files/do_brk _fix.patch ============================ can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/mm/mmap.c Fri Sep 12 06:44:06 2003 |+++ b/mm/mmap.c Thu Oct 2 01:18:19 2003 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p3 < /usr/portage/sys-kernel/gentoo-sources/files/do_brk _fix.patch ============================ missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/mm/mmap.c Fri Sep 12 06:44:06 2003 |+++ b/mm/mmap.c Thu Oct 2 01:18:19 2003 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p4 < /usr/portage/sys-kernel/gentoo-sources/files/do_brk _fix.patch ============================ missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/mm/mmap.c Fri Sep 12 06:44:06 2003 |+++ b/mm/mmap.c Thu Oct 2 01:18:19 2003 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored -----------------------------------------------------------till here
Fixed in CVS; Thanks!
*** Bug 739616 has been marked as a duplicate of this bug. ***
