From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] package/linux/Makefile.in does not include 'openswan' patches
Date: Mon, 23 Jul 2007 17:19:36 +0200 [thread overview]
Message-ID: <000401c7cd42$28b0cec0$dcc4af0a@atmel.com> (raw)
In-Reply-To: 20070723142207.GA9324@aon.at
> On Mon, Jul 23, 2007 at 03:29:36PM +0200, Bernhard Fischer wrote:
>>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).
>
> ok, you broke building a linux kernel.
>
No, Stephen did...
He patched the linux makefile with the BSP patch.
Please give the credit where it is due.
> excerpt:
> make[1]: Leaving directory
> `/scratch/obj.i686/buildroot.mine/toolchain_build_i386/module-init-tools-3.2.2'
> touch -c
> /scratch/obj.i686/buildroot.mine/toolchain_build_i386/module-init-tools-3.2.2/depmod
> /usr/bin/install -D
> /scratch/obj.i686/buildroot.mine/toolchain_build_i386/module-init-tools-3.2.2/depmod
> /scratch/obj.i686/buildroot.mine/build_i386/staging_dir/bin/i386-linux-depmod26
> make: *** No rule to make target
> `/scratch/obj.i686/buildroot.mine/project_build_i386//linux-2.6.21.5/.patched',
> needed by
> `/scratch/obj.i686/buildroot.mine/project_build_i386//linux-2.6.21.5/.configured'.
> Stop.
>
>
> This is due to this PROJECT thing. Please revert immediately or fix ASAP.
>
> While i understand that it's possible that one thing or another can
> break in the course of changes, i ask you to be more careful.
>
Please be more careful in who you are addressing your comments.
Furthermore, it would be more constructive to patch the module-init-tools.
I generated the linux-experimental directory, to be able to do more tests and I got flak for that.
> regards,
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-07-23 15:19 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
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 [this message]
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='000401c7cd42$28b0cec0$dcc4af0a@atmel.com' \
--to=ulf@atmel.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