From: Babarovic Ivica <ivica.babarovic@asist.si>
To: buildroot@busybox.net
Subject: [Buildroot] svn At revision 20289 breakage
Date: Fri, 19 Oct 2007 10:13:19 +0200 [thread overview]
Message-ID: <4718671F.3040005@asist.si> (raw)
In-Reply-To: <008201c81224$6c96bd80$01c4af0a@Glamdring>
Ulf Samuelsson wrote:
>
> It is always the case that you have to provide a ".config" file for
> linux.
>
> For some lucky souls Buildroot will do it for you.
> This is when there is an appropriate definition somewhere in the
> target directory,
> and if you have supplied the right kernel.
Well, I guess I was lucky until now. I never provided any kernel or
.config files.
I still fail to see why this is important for buildroot build. Kernel
headers?
I have a .config file from a kernel I build. Should I put that into
buildroot process?
What differences would it make?
>
> For some unlucky souls, they now have an option to start a "make xconfig"
> to get a window allowing them to configure things instead of having a
> failed build.
>
next prev parent reply other threads:[~2007-10-19 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 18:22 [Buildroot] svn At revision 20289 breakage Babarovic Ivica
2007-10-18 20:59 ` Ivan Kuten
2007-10-18 20:20 ` Ulf Samuelsson
2007-10-18 21:31 ` Ivan Kuten
2007-10-18 20:33 ` Ulf Samuelsson
2007-10-18 20:36 ` Ulf Samuelsson
2007-10-18 21:58 ` Ivan Kuten
2007-10-19 6:39 ` Babarovic Ivica
2007-10-19 7:32 ` Babarovic Ivica
2007-10-19 7:45 ` Ulf Samuelsson
2007-10-19 8:13 ` Babarovic Ivica [this message]
2007-10-19 8:20 ` Ulf Samuelsson
2007-10-19 10:21 ` Kuten Ivan
2007-10-19 8:35 ` Ulf Samuelsson
2007-10-19 10:45 ` Kuten Ivan
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=4718671F.3040005@asist.si \
--to=ivica.babarovic@asist.si \
--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