Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error encountered while doing make after adding u-boot
Date: Mon, 26 Jan 2009 15:17:32 +0100	[thread overview]
Message-ID: <20090126151732.7c6aa021@hcegtvedt> (raw)
In-Reply-To: <87wsci88t8.fsf@macbook.be.48ers.dk>

On Mon, 26 Jan 2009 15:02:11 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:

> >>>>> "Hans-Christian" == Hans-Christian Egtvedt
> >>>>> <hans-christian.egtvedt@atmel.com> writes:
> 
>  Hans-Christian> On Mon, 26 Jan 2009 18:36:16 +0530
>  Hans-Christian> Mitesh Gupta <guptamitesh@gmail.com> wrote:
> 
>  Hans-Christian> <snipp>
> 
>  >> make[1]: Entering directory
>  >> `/mnt/rootfs/buildroot/project_build_i686/uclibc/u-boot-2008.10'
>  >> make[1]: *** No rule to make target `_config'.  Stop.
> 
>  Hans-Christian> You need to set the variable
> BR2_TARGET_UBOOT_BOARDNAME.
> 
> Why is it again we don't default to $(PROJECT) for this?
> 
> This BOARD_NAME variable seems to be an ARM/Atmel specific thing.
> 

You can not default to $(PROJECT), since this variable is used to load
a configuration for u-boot build system and must exist.

Perhaps default to a known to work config? Take a peak in u-boot
source ./Makefile.

-- 
Best regards,
Hans-Christian Egtvedt

  reply	other threads:[~2009-01-26 14:17 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 [this message]
2009-01-26 14:24       ` Peter Korsgaard
2009-01-26 14:30         ` Hans-Christian Egtvedt
2009-01-26 14:50           ` Peter Korsgaard
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=20090126151732.7c6aa021@hcegtvedt \
    --to=hans-christian.egtvedt@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