From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] oddity with project_ vs. kernel dir
Date: Tue, 18 Sep 2007 18:30:08 +0200 [thread overview]
Message-ID: <20070918163008.GA14096@aon.at> (raw)
Ulf,
I'm trying to build a kernel with openswan (for i386, for example).
Everything works as expected when generating and installing the
kernel-headers ??) but the, when unpacking/patching the kernel for the
target, soomebody seems to try to apply a duplicate patch:
rm -rf
/scratch/obj.i686/buildroot_trunk/project_build_i386/uclibc/linux-2.6.22.6
*** Unpacking kernel source
bzcat /scratch/obj.i686/buildroot_trunk/down/linux-2.6.22.6.tar.bz2 |
tar -C /scratch/obj.i686/buildroot_trunk/project_build_i386/uclibc -xf -
touch /scratch/obj.i686/buildroot_trunk/project_build_i386/uclibc/linux-2.6.22.6/.unpacked
toolchain/patch-kernel.sh /scratch/obj.i686/buildroot_trunk/project_build_i386/uclibc/linux-2.6.22.6
toolchain/kernel-headers \
linux-2.6.22.6-\*.patch{,.gz,.bz2}
toolchain/patch-kernel.sh /scratch/obj.i686/buildroot_trunk/toolchain_build_i386/linux-2.6.22.6
package/openswan \
linux-2.6.22.6-\*.patch{,.gz,.bz2}
Applying linux-2.6.22.6-openswan-2.4.9.kernel-2.6-klips.patch using
plaintext:
The next patch would create the file README.openswan-2,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
(a bit line-wrapped, sorry).
Does that sound familiar to you?
??):
touch
/scratch/obj.i686/buildroot_trunk/toolchain_build_i386/linux-2.6.22.6/.unp
acked
toolchain/patch-kernel.sh
/scratch/obj.i686/buildroot_trunk/toolchain_build_i386
/linux-2.6.22.6 toolchain/kernel-headers \
linux-2.6.22.6-\*.patch{,.gz,.bz2}
toolchain/patch-kernel.sh
/scratch/obj.i686/buildroot_trunk/toolchain_build_i386
/linux-2.6.22.6 package/openswan \
linux-2.6.22.6-\*.patch{,.gz,.bz2}
Applying linux-2.6.22.6-openswan-2.4.9.kernel-2.6-klips.patch using
plaintext:
patching file README.openswan-2
patching file crypto/ciphers/aes/test_main.c
patching file crypto/ciphers/aes/test_main_mac.c
patching file include/crypto/aes.h
[snip rest of stuff working fine for kernel-headers]
patching file net/ipsec/Makefile.ver
Applying linux-2.6.22.6-openswan-2.4.9.kernel-2.6-natt.patch using
plaintext:
patching file include/net/xfrmudp.h
patching file net/ipv4/Kconfig
patching file net/ipv4/udp.c
touch /scratch/obj.i686/buildroot_trunk/toolchain_build_i386/linux-2.6.22.6/.patched
next reply other threads:[~2007-09-18 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 16:30 Bernhard Fischer [this message]
2007-09-18 17:10 ` [Buildroot] oddity with project_ vs. kernel dir Bernhard Fischer
2007-09-21 15:33 ` [Buildroot] using PROJECTs with buildroot Bernhard Fischer
[not found] ` <20070924123117.GA1010@aon.at>
2007-09-24 14:43 ` Ulf Samuelsson
2007-09-24 18:48 ` Bernhard Fischer
2007-09-24 19:47 ` Ulf Samuelsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070918163008.GA14096@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox