From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot building problems
Date: Fri, 18 Jan 2008 09:42:20 +1100 [thread overview]
Message-ID: <20080117224220.GA26760@cloud.net.au> (raw)
In-Reply-To: <20080117160206.GB3086@aon.at>
On Thu, Jan 17, 2008 at 05:02:06PM +0100, Bernhard Fischer wrote:
> On Thu, Jan 17, 2008 at 06:41:07PM +0300, Yegor Masharsky wrote:
> >Hi all ,
> >
> >I'm trying to setup buildroot and uclibc on my host , but something
> >goes wrong . According to buildroot manual I've downloaded buildroot
> >using
>
> grep KCONFIG .config
> see docs/README
Maybe target/linux/Makefile.in could be modified to give an error if
BR2_PACKAGE_LINUX_KCONFIG is unset, rather than just using it blindly?
It already gives an error if the variable is set to a non-existent file.
That would prevent approximately one post/bug report per week.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-01-17 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 15:41 [Buildroot] buildroot building problems Yegor Masharsky
2008-01-17 16:02 ` Bernhard Fischer
2008-01-17 17:17 ` Yegor Masharsky
2008-01-17 17:41 ` Bernhard Fischer
2008-01-17 22:42 ` Hamish Moffatt [this message]
2008-01-17 23:14 ` Bernhard Fischer
2008-01-17 19:35 ` Paul
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=20080117224220.GA26760@cloud.net.au \
--to=hamish@cloud.net.au \
--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