[Aboriginal] Kernel patching failure with 184.108.40.206
rob at landley.net
Fri Sep 6 18:31:31 PDT 2013
On 09/02/2013 06:23:08 AM, Patrick Lauer wrote:
> On 09/02/2013 05:31 PM, Rob Landley wrote:
> > On 08/30/2013 12:58:35 AM, Patrick Lauer wrote:
> >> On 08/18/2013 11:57 AM, Patrick Lauer wrote:
> >> > Trying to build 220.127.116.11 fails when fetching/patching kernel:
> >> > patching file init/Kconfig
> >> > Hunk #1 succeeded at 1797 (offset 131 lines).
> >> > Applying
> >> >
> >> > The next patch would create the file kernel/Makefile,
> >> > which already exists! Assume -R? [n]
> >> > Apply anyway? [n]
> >> > Skipping patch.
> >> > 1 out of 1 hunk ignored
> >> > patching file kernel/timeconst.bc
> >> > patching file kernel/Makefile
> >> > Hunk #1 succeeded at 126 (offset 1 line).
> >> >
> >> > Exiting due to errors (host download linux)
> >> >
> >> > Exiting due to errors ( )
> >> This is due to a change in behaviour with patch - version <=2.6.1
> >> fine, >=2.7 fail.
> > And _this_ is why I build host-tools.sh to isolate the build from
> > random gnu regressions. (Alas, there's a chicken and egg problem in
> > protecting download.sh or host-tools.sh from this stuff.)
> Then you'd end up at some point carrying your own statically-built
> everything, only relying on some archiver like cpio/tar/zip for the
> initial unpacking
Except I'm not assuming the build host is x86. :)
No, we've gotta start somewhere, and the current host-tools.sh is as
generic as I can get.
> > Where do I get a test system that displays this problem? (I don't
> > anything with patch 2.7 installed. Should I build a linux from
> > or is there something I can install into a qemu image by just
> > an iso...?)
> I upgraded patch on my server, so you can reproduce it there.
I just did a fresh EXTRACT_ALL=1 there and it worked.
Admittedly it worked against 3.11 instead of 3.10, but the patch in
question created a new file...
Does this still reproduce for you?
More information about the Aboriginal