From: Ron Eggler <reggler@semios.com>
To: buildroot@busybox.net
Subject: [Buildroot] generate uImage file
Date: Wed, 18 Dec 2013 05:57:26 +0000 [thread overview]
Message-ID: <1776243.gWOYWTpOXo@regdesktophome> (raw)
In-Reply-To: <20131218104644.364648bc@skate>
> Dear Ron Eggler,
>
> On Tue, 17 Dec 2013 21:50:50 +0000, Ron Eggler wrote:
> > I just changed my buildroot config to generate a uImage file. I then
> > did a "make clean" followed by a make but for both I get:
> > linux/linux.mk:339: *** No kernel configuration file specified, check
> > your BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE setting. Stop.
> >
> > What does this mean? How do I fix this to compile again?
>
> You have selected the choice of providing a kernel configuration file
> to configure the kernel, but you did not give Buildroot the path to
> this file with the BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE configuration
> option.
That was it, providing the path under "configuration file path" fixed the issue.
Thank you Thomas!
Ron
--
*ron eggler | semios | senior software engineer*
320 - 887 Great Northern Way | Vancouver, BC | V5T 4T5
T | 604 229 2044 ext 105[1]
C | 778 230 9442[2]
E | reggler at semios.com[3]
smart farming[4]
twitter[5] linkedin[6]
--------
[1] tel:604%20229%202044%20ext%20105
[2] tel:778%20230%209442
[3] mailto:reggler at semios.com
[4] http://www.semios.com
[5] https://twitter.com/semios
[6] http://www.linkedin.com/company/semiosbio-technologies-inc?goback=%2Enmp_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1&trk=company_logo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131218/5b11e570/attachment.html>
prev parent reply other threads:[~2013-12-18 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 21:50 [Buildroot] generate uImage file Ron Eggler
2013-12-18 9:46 ` Thomas Petazzoni
2013-12-18 5:57 ` Ron Eggler [this message]
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=1776243.gWOYWTpOXo@regdesktophome \
--to=reggler@semios.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