All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad House <brad@mainstreetsoftworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] kernel-headers: lzma causing issues
Date: Wed, 15 Aug 2007 07:51:55 -0400	[thread overview]
Message-ID: <46C2E8DB.5020309@mainstreetsoftworks.com> (raw)
In-Reply-To: <1187165518.4942.6.camel@elrond.sweden.atmel.com>

>> +config BR2_KERNEL_HEADERS_LZMA
>> +	bool "use lzma initramfs kernel patches"
>> +	default y
>> +	help
>> +	  Apply patches which allow for lzma compressed
>> +	  initramfs filesystems.  This requires the lzma
>> +	  program in your development environment.	
>> +
> 
> Since it also breaks unless you have lzma causing headache, 
> I think the default should be to not use the lzma patch...

ok, yeah, I'd agree with that ... I was just maintaining
compatibility for those who are using it by defaulting to y.

> I am working on a new scheme where the target/linux and
> toolchain/kernel-headers are integrated, but this
> needs a lot more testing and will (as agreed with Bernhard
> be reviewed before applied, but it seems reasonable
> to do this as an intermediate fix.

Ah, yeah, it would definitely make sense for those to be
integrated. It took me a minute to realize the kernel
headers version is what determined which release of the
kernel got built ;)

Thanks.
-Brad

  reply	other threads:[~2007-08-15 11:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15  0:57 [Buildroot] [patch] kernel-headers: lzma causing issues Brad House
2007-08-15  8:11 ` Ulf Samuelsson
2007-08-15 11:51   ` Brad House [this message]
2007-08-15 14:40     ` Ulf Samuelsson

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=46C2E8DB.5020309@mainstreetsoftworks.com \
    --to=brad@mainstreetsoftworks.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.