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: Tue, 14 Aug 2007 20:57:35 -0400	[thread overview]
Message-ID: <46C24F7F.1020203@mainstreetsoftworks.com> (raw)

The lzma patches really should be optional, so I've attached a patch
which does exactly that.

I find myself having to remove the lzma patches because my build system
doesn't natively have lzma.  I tried to compensate for this by
installing the latest lzma from gentoo's package tree, and apparently,
it accepts different flags than the one these patches expect, so my
kernel build still fails.  Finally, I used the lzma from this buildroot
and compiled it by hand, and it _mostly_ worked.  Regardless, it seems
silly to make this a requirement.  Personally, I gzip my initramfs,
and that's enough compression for me...

Please apply this patch and create a toolchain/kernel-headers/lzma
directory and move the linux-*lzma*.patch files to that directory.
I'm sure I can't be the only person who's had to simply delete those
patches from my tree.

Thanks.
-Brad
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: kernel-headers-lzma-optional.diff
Url: http://busybox.net/lists/buildroot/attachments/20070814/3c555d82/attachment.diff 

             reply	other threads:[~2007-08-15  0:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15  0:57 Brad House [this message]
2007-08-15  8:11 ` [Buildroot] [patch] kernel-headers: lzma causing issues Ulf Samuelsson
2007-08-15 11:51   ` Brad House
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=46C24F7F.1020203@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.