From: Mark Jackson <mpfj-list@mimc.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with defconfig
Date: Thu, 24 Sep 2009 11:50:59 +0100 [thread overview]
Message-ID: <4ABB4F13.9060102@mimc.co.uk> (raw)
In-Reply-To: <87eipxrfz0.fsf@macbook.be.48ers.dk>
Peter Korsgaard wrote:
<snip>
>
> %_defconfig: $(CONFIG)/conf
> cp $(shell find ./target/ -name $@) .config
> -@$(MAKE) oldconfig
>
> So I don't get it why it doesn't trigger for you. Does a simple 'make
> blah_defconfig' work for you?
The makefile seems to be looking for the file, but can't find it:-
mpfj at mpfj-x64:~/avr32/buildroot$ make --debug atngw100-base_defconfig
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for x86_64-pc-linux-gnu
Reading makefiles...
Updating goal targets....
File `atngw100-base_defconfig' does not exist.
Must remake target `atngw100-base_defconfig'.
make: *** No rule to make target `atngw100-base_defconfig'. Stop.
mpfj at mpfj-x64:~/avr32/buildroot$
next prev parent reply other threads:[~2009-09-24 10:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 10:08 [Buildroot] Problem with defconfig Mark Jackson
2009-09-23 10:24 ` Peter Korsgaard
2009-09-23 10:53 ` Mark Jackson
2009-09-23 11:05 ` Peter Korsgaard
2009-09-23 11:13 ` Mark Jackson
2009-09-23 12:41 ` Peter Korsgaard
2009-09-23 12:45 ` Mark Jackson
2009-09-23 13:01 ` Peter Korsgaard
2009-09-23 14:09 ` Mark Jackson
2009-09-23 20:03 ` Peter Korsgaard
2009-09-24 10:50 ` Mark Jackson [this message]
2009-09-24 15:42 ` Thiago A. Corrêa
2009-09-24 15:48 ` Peter Korsgaard
2009-09-24 16:33 ` [Buildroot] Foreigh toolchain Michael Trimarchi
2009-09-24 18:28 ` Thomas Petazzoni
2009-09-25 7:35 ` Michael Trimarchi
2009-09-24 10:45 ` [Buildroot] Problem with defconfig Mark Jackson
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=4ABB4F13.9060102@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--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