Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel Download Error with external toolchain
Date: Sat, 29 Sep 2007 19:10:31 +0200	[thread overview]
Message-ID: <20070929171031.GQ20951@aon.at> (raw)
In-Reply-To: <1191084620.7864.16.camel@venture.bit63.org>

On Sat, Sep 29, 2007 at 12:50:20PM -0400, Clark Rawlins wrote:

>Let me rephrase to make sure I understand what you are saying.

>How close am I? :)

Yes, that'd be it.
For the dependency stuff (project_/$PROJ/buildroot-config), i'd prefer
to keep the names in the BR2_KERNEL_* hierarchy. A bit clumsy,
but nicer for the wildcards.

config BR2_KERNEL_SRC_IS_HEADERS
	bool "Use kernel tarball for both headers and kernel-binary"
	default y
	help
	  selfexplanatory but could need a more elaborate text

BR2_PACKAGE_LINUX_SRC_VERSION
	string "linux kernel version"
	default ""
	depends on !BR2_KERNEL_SRC_IS_HEADERS
	help
	  Specify the version of the linux kernel to use to
	  build the kernel binary.

or something like this

      reply	other threads:[~2007-09-29 17:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 13:18 [Buildroot] Kernel Download Error with external toolchain Clark Rawlins
2007-09-28 18:08 ` Bernhard Fischer
2007-09-28 18:16   ` Clark Rawlins
2007-09-28 18:20     ` Bernhard Fischer
2007-09-28 19:01   ` Ulf Samuelsson
2007-09-28 19:16     ` Bernhard Fischer
2007-09-28 20:49       ` Clark Rawlins
2007-09-28 20:58         ` Bernhard Fischer
2007-09-29 16:50           ` Clark Rawlins
2007-09-29 17:10             ` Bernhard Fischer [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=20070929171031.GQ20951@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