From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Support for MPC_8323E-RDB Board
Date: Fri, 4 Nov 2016 14:59:37 +0100 [thread overview]
Message-ID: <20161104145937.174c3cb6@free-electrons.com> (raw)
In-Reply-To: <CANO2Q2-50CT2crNwtt8s7oyh_n+s0ukZ=zqT+R_8EtKh0+jg-w@mail.gmail.com>
Hello,
On Fri, 4 Nov 2016 18:03:38 +0530, Siva Prakash Reddy Nareddy wrote:
> The issues I am getting are as follows..
>
> jyothi at jyothi:/home/buildroot-labs/buildroot$ sudo make menuconfig
Don't run Buildroot as root.
> configuration written to /home/buildroot-labs/buildroot/.config
>
> *** End of the configuration.
> *** Execute 'make' to start the build or try 'make help'.
>
> jyothi at jyothi:/home/buildroot-labs/buildroot$ sudo make
> boot/uboot/uboot.mk:295: *** No board defconfig name specified, check your
> BR2_TARGET_UBOOT_DEFCONFIG setting. Stop.
This means you have enabled the U-Boot bootloader, but you have not
defined which U-Boot configuration to build, so Buildroot cannot start
the build process.
> jyothi at jyothi:/home/buildroot-labs/buildroot$ sudo make
> linux/linux.mk:441: *** No kernel device tree source specified, check your
> BR2_LINUX_KERNEL_USE_INTREE_DTS / BR2_LINUX_KERNEL_USE_CUSTOM_DTS
> settings. Stop.
This means you have enabled the Linux kernel, with Device Tree support,
but you haven't specified which Device Tree files you want to build.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-04 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 12:33 [Buildroot] Support for MPC_8323E-RDB Board Siva Prakash Reddy Nareddy
2016-11-04 13:59 ` Thomas Petazzoni [this message]
2016-11-04 21:37 ` Arnout Vandecappelle
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=20161104145937.174c3cb6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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