From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Error encountered while doing make after adding u-boot
Date: Mon, 26 Jan 2009 15:50:27 +0100 [thread overview]
Message-ID: <87ocxu86ks.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090126153034.21798ced@hcegtvedt> (Hans-Christian Egtvedt's message of "Mon\, 26 Jan 2009 15\:30\:34 +0100")
>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:
>> Naah, to much work as that's arch dependent. Then I would rather add a
>> big fat $(error) in the U-Boot Makefile.in if the thing evaluates to
>> nothing.
>>
Hans-Christian> ... I think checking for an empty config name is
Hans-Christian> better, and print an appropriate message before
Hans-Christian> quiting. If the PROJECT happens to work, that still
Hans-Christian> might not be the u-boot config the user wants, and
Hans-Christian> he/she does not understand why u-boot does not work
Hans-Christian> afterwards.
Ok, done - It gives something like:
target/u-boot/Makefile.in:287: *** NO U-Boot board name set. Check your BR2_TARGET_UBOOT_BOARDNAME setting. Stop.
That seems pretty clear to me.
Hans-Christian> And in most instances the PROJECT name will not match
Hans-Christian> a U-Boot config.
Maybe, in the kind of setup I'm normally doing it does, but maybe not
for others.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-26 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 13:06 [Buildroot] Error encountered while doing make after adding u-boot Mitesh Gupta
2009-01-26 13:40 ` Hans-Christian Egtvedt
2009-01-26 14:02 ` Peter Korsgaard
2009-01-26 14:17 ` Hans-Christian Egtvedt
2009-01-26 14:24 ` Peter Korsgaard
2009-01-26 14:30 ` Hans-Christian Egtvedt
2009-01-26 14:50 ` Peter Korsgaard [this message]
2009-01-27 0:24 ` 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=87ocxu86ks.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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