Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Sagaert <sagaert.johan@proximus.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] build host lz4 to support lz4 compression in the kernel.
Date: Wed, 01 Apr 2015 22:24:15 +0200	[thread overview]
Message-ID: <551C53EF.6070806@proximus.be> (raw)
In-Reply-To: <20150401150237.4cabd12a@free-electrons.com>

Dear Thomas ,
Posted v2 patch minutes ago.

Thomas Petazzoni schreef op 1/04/2015 om 15:02:

> Dear Johan Sagaert,
>
> On Wed, 01 Apr 2015 14:25:38 +0200, Johan Sagaert wrote:
>
>>> I think it's time to add some Config.in options in linux/Config.in to
>>> select the compression tools to be made available, and enforce their
>>> usage/availability in the Linux .config file. It is annoying to bvuild
>>> host-lzop and host-lz4 every time you're building a kernel if you don't
>>> care about those compressions algos.
>> I am not sure if all kernel releases have the lz4 compression option, so
>> this
>> seemed the most simple solution, lz4 is not taking large resources in
>> terms of build time
>> This works fine for me now.
> Yes, it works. But everyone now needs to build host-lzop and host-lz4
> before building a kernel even if they don't work.
>
>> Not sure about this : could host-lz4 be build in a kernel_pre_build hook ?
>> checking the kernels .config  before the kernel build starts.
> Unfortunately, no. The dependencies have to be known before the kernel
> configuration is generated.
Changed the patch so that host-lz4 is only build when the target is ARM .
That should reduce clutter.
If some make expert could show me how to use the LINUX_VERSION_PROBED 
variable
to check for >=3.11 it would further reduce unneeded builds.
>> I don't want lz4 on the target , that is why i have done it this way,
>> lz4 that can be selected via the menu
>> if needed on the target , and a host-lz4 that is always build when
>> building a kernel.
>> Sent me your suggestion, and i will try to fix this patch. (have to do
>> all buildroot patchwork in free-time )
> Just don't do *any* change to the lz4 package. Add your host-lz4
> dependency to LINUX_DEPENDENCIES, and this is enough. It will only
> build the host variant of lz4. The target variant will only be built if
> BR2_PACKAGE_LZ4 is enabled in your Buildroot .config.
>
> You seem to believe that because the target and host variant of lz4 are
> implemented in the same .mk file, both of them are always built
> together. But this is not the case. Even with both defined in the
> same .mk file, it perfectly supports building only the host variant,
> only the target variant, or both.
>
> So your change to lz4.mk and creating a host-lz4.mk is completely
> unnecessary.
Yes, i was in this misconception.

> Best regards,
>
> Thomas

Best Regards , Johan

      parent reply	other threads:[~2015-04-01 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 10:30 [Buildroot] [PATCH 1/1] build host lz4 to support lz4 compression in the kernel Sagaert Johan
2015-04-01 11:37 ` Thomas Petazzoni
2015-04-01 12:25   ` Johan Sagaert
2015-04-01 13:02     ` Thomas Petazzoni
2015-04-01 13:17       ` Thomas Petazzoni
2015-04-01 20:24       ` Johan Sagaert [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=551C53EF.6070806@proximus.be \
    --to=sagaert.johan@proximus.be \
    --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