[Buildroot] [PATCH 0/2] use host compressor for rootfs

[Philippe Reynes]

Hi Thomas,

I've experienced a weird behavior with lzma.
We are using lzma to compress initramfs.

On an old buildroot where the local lzma was used.

It was working fine on some machine, but it fails
on others. The fails was a "not enought memory"
at boot time. Of course, it was also an old kernel.
I never understood why using local lzma raise
this issue.


After we add a dependency to "host-lzma",
it works everywhere.

So using host-<compressor> fix this issue, and
now we have the same behavior on all desktop.

This serie is based on : if it could happen on 

lzma, it could happen on gzip/bzip2.


Regards,
Philippe


Le Dimanche 6 avril 2014 11h32, Thomas De Schampheleire <patrickdepinguin at gmail.com> a écrit :
 
Philippe Reynes <tremyfr at yahoo.fr> schreef:

>Hi Baruch,
>
>I've missed this "mandatory dependancy".
>I suppose that this dependancy is usefull to uncompress tarball.
>But I think that the compilation of firmware should be done with
>tools compiled by buildroot.
>
>If lzma is used to compress the rootfs, then lzma is compile
>by builtoot. If gzip is used to compress the rootfs, then we use
>local gzip. It's not very "coherent".
>And using compiled binary with buildroot increase chance to
>regenerate firmware on (very) different machine.
>
>And I agree with you, it's not a "real" issue, it's more a "nice to have".

The problem is that the build time is increased without good reason.
If there is a problem with a specific version of gzip/bzip2, we could always use the suitable-host-package mechanism as we do for tar. In fact, you could start using it for lzma too and avoid building host-lzma if it's already present...

Best regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20140406/7000f352/attachment-0001.html>