From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel build process
Date: Thu, 1 Jul 2010 08:45:12 +0200 [thread overview]
Message-ID: <20100701084512.5146e5a1@surf> (raw)
In-Reply-To: <000f01cb18a2$d4f5fad0$7ee1f070$@pauljones.id.au>
On Thu, 1 Jul 2010 08:22:55 +1000
"Paul Jones" <paul@pauljones.id.au> wrote:
> Good point. I guess if we tell the user to run "make
> linux26-menuconfig" that would be just as good.
Or to give a configuration file or defconfig name. The problem with
"make linux26-menuconfig" is that the configuration of the kernel will
be stored in output/build/linux-..../.config, and being part of the
output/ directory, it will be removed if the user doesn't save it
elsewhere.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-01 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 11:03 [Buildroot] Kernel build process Paul Jones
2010-06-30 16:58 ` Thomas Petazzoni
2010-06-30 22:22 ` Paul Jones
2010-07-01 6:45 ` Thomas Petazzoni [this message]
2010-07-01 7:01 ` Paul Jones
2010-06-30 17:04 ` Thiago A. Corrêa
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=20100701084512.5146e5a1@surf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.