Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:25:33 +0200	[thread overview]
Message-ID: <000501c7cd42$2a1b0d20$dcc4af0a@atmel.com> (raw)
In-Reply-To: 20070723144314.GC9324@aon.at

----- Original Message ----- 
From: "Bernhard Fischer" <rep.dot.nop@gmail.com>
To: "Ulf Samuelsson" <ulf@atmel.com>
Cc: "buildroot" <buildroot@uclibc.org>
Sent: Monday, July 23, 2007 4:43 PM
Subject: Re: [Buildroot] package/linux/Makefile.in does not include 'openswan' patches


> On Mon, Jul 23, 2007 at 04:22:07PM +0200, Bernhard Fischer wrote:
>>On Mon, Jul 23, 2007 at 03:29:36PM +0200, Bernhard Fischer wrote:
> 
>>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.
> 
> By now i have reverted these incorrect hunks in svn.
>>

You did not fix this, since you assume that the kernel headers and the kernel is the same.
If they are not, the bug is still there, so it is NOT because of the BSP stuff,
and you fixed the symptom, not the cause.
Try setting LINUX26_VERSION to 2.6.22.1 and build with openswan,
and you see what I mean.

>>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.
> 
> I suggest you
> ifneq ($(PROJECT_BUILD_DIR),)
> fixup_after_ulf=O=$(PROJECT_BUILD_DIR)
> endif
> LINUX26_MAKE_FLAGS+=$(fixup_after_ulf)
> 
> but you were about to do the same anyway, weren't you..
>

No, I want to have two ways of building linux, 
until the BSP stuff is fully tested, and then merge into one.
Not fill the single linux makefile with a lot of kludges
which has no long term validity.

Best Regards
Ulf Samuelsson

  reply	other threads:[~2007-07-23 15:25 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 [this message]
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='000501c7cd42$2a1b0d20$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