From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Not Using Saved Config for Linux
Date: Wed, 07 Jan 2009 11:30:28 +0100 [thread overview]
Message-ID: <1231324228.32308.285.camel@elrond.atmel.com> (raw)
In-Reply-To: <BAY124-W513BAFC261A9EA054E0337D2DE0@phx.gbl>
tis 2009-01-06 klockan 14:43 -0800 skrev Quick X:
> Ahh, I just noticed that this bug was already subitted here a few months ago at:
> http://lists.busybox.net/pipermail/buildroot/2008-November/024028.html
This line is the problem.
target/device/Atmel/Makefile.in:LINUX26_KCONFIG:=
$(BOARD_PATH)/$(BOARD_NAME)-linux-$(LINUX26_VERSION).config
This forces the linux to ALWAYS try the config
with an identical kernel major/minor first
if there is one in the board directory.
Not so useful if you have your own project...
Comment that out, and it will work.
The real solution is elsewhere.
I think that if the make saveconfig needs to be updated
so that BR2_BOARD_PATH is $(LOCAL)/$(PROJECT)
I just committed that.
If you update the svn then it might work.
> He words the problem better than I. Cheers, NB
> _________________________________________________________________
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2009-01-07 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 23:11 [Buildroot] Buildroot Not Using Saved Config for Linux Quick X
2009-01-06 1:34 ` [Buildroot] Cups compile problem Daniel
2009-01-06 4:24 ` [Buildroot] _Cups_compile_problem Daniel
2009-01-06 18:31 ` [Buildroot] Buildroot Not Using Saved Config for Linux Ulf Samuelsson
2009-01-06 20:40 ` Quick X
2009-01-06 22:43 ` Quick X
2009-01-07 10:30 ` Ulf Samuelsson [this message]
2009-01-07 20:51 ` Quick X
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=1231324228.32308.285.camel@elrond.atmel.com \
--to=ulf.samuelsson@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