From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot building problems
Date: Thu, 17 Jan 2008 18:41:47 +0100 [thread overview]
Message-ID: <20080117174147.GA3609@aon.at> (raw)
In-Reply-To: <53499b480801170917v714fca95t17138a23d0740905@mail.gmail.com>
On Thu, Jan 17, 2008 at 08:17:28PM +0300, Yegor Masharsky wrote:
>Hello Bernhard ,
>
>grep KCONFIG .config returns
>BR2_PACKAGE_LINUX_KCONFIG=""
>
>docs/README says :
>
>1) run 'make menuconfig'
>2) select the packages you wish to compile
>3) run 'make'
>4) wait while it compiles
>5) Use your shiny new root filesystem. Depending on which sortof
> root filesystem you selected, you may want to loop mount it,
> chroot into it, nfs mount it on your target device, burn it
> to flash, or whatever is appropriate for your target system.
>
>So I fail at step 4 but don't see where I missed something
read on, your're not EOF there :)
next prev parent reply other threads:[~2008-01-17 17:41 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 [this message]
2008-01-17 22:42 ` Hamish Moffatt
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=20080117174147.GA3609@aon.at \
--to=rep.dot.nop@gmail.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