From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] package/linux/Makefile.in does not include 'openswan' patches
Date: Mon, 23 Jul 2007 15:29:36 +0200 [thread overview]
Message-ID: <20070723132936.GB7902@aon.at> (raw)
In-Reply-To: <1185196286.21840.18.camel@elrond.sweden.atmel.com>
On Mon, Jul 23, 2007 at 03:11:26PM +0200, Ulf Samuelsson wrote:
>The Kernel Headers buildscript applies the openswan patches
>on top of the kernel headers, but the target/linux/Makefile.in does not.
The headers (which used the very same sourcedir, dunno if it still does
with your toolchain/linux* stuff) have to be patched. To achieve this,
we patch the source before installing the headers.
>
>Isn't this a bug?
I don't understand? You can't apply patches twice, if you mean to
suggests this (you most likely don't, i assume).
next prev parent reply other threads:[~2007-07-23 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 13:11 [Buildroot] package/linux/Makefile.in does not include 'openswan' patches Ulf Samuelsson
2007-07-23 13:29 ` Bernhard Fischer [this message]
2007-07-23 14:19 ` Ulf Samuelsson
2007-07-23 14:22 ` Bernhard Fischer
2007-07-23 14:43 ` Bernhard Fischer
2007-07-23 15:25 ` Ulf Samuelsson
2007-07-23 16:33 ` [Buildroot] "multiple target patterns" error while building under cygwin Crane, Matthew
2007-07-25 14:33 ` Rex Ashbaugh
[not found] ` <20070727162707.GH25147@aon.at>
2007-07-27 17:04 ` Crane, Matthew
2007-07-27 18:05 ` Bernhard Fischer
2007-07-23 16:56 ` [Buildroot] package/linux/Makefile.in does not include 'openswan' patches Bernhard Fischer
2007-07-23 15:19 ` Ulf Samuelsson
2007-07-23 16:41 ` Bernhard Fischer
2007-07-23 19:38 ` 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=20070723132936.GB7902@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