[Buildroot] JFFS2 / MTD suggestions

Peter Korsgaard jacmet at uclibc.org
Wed Apr 8 14:59:11 UTC 2009

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com> writes:


 >> Or even better, compile lzo for the host and link against that.

 Thomas> I know that's what we do for automake, autoconf, pkg-config, m4 and a
 Thomas> bunch of other stuff. But I must admit, that personnaly, I'm not
 Thomas> really a fan of this. I would rather prefer to leverage what's
 Thomas> installed on the host, and consider that Buildroot having dependencies
 Thomas> on installed packages (liblzo-dev and others) is normal.

Yes, that works as long as the dependencies are stable and we can work
with the various versions available. That's unfortunately often not
the case, and then the easiest solution is to simply build it

I think lzo clearly fits in the:

 - Not available on most systems
 - Small and hence quick to compile
 - Users (mkfs.jffs2) needs a fairly specific version


 Thomas> Currently, one of the strong advantage of Buildroot compared
 Thomas> to more heavyweight solutions like OpenEmbedded is that the
 Thomas> time for Buildroot checkout to the first basic root
 Thomas> filesystem being produced is very small (15 minutes or
 Thomas> so). If we start compiling more and more host tools to the
 Thomas> point that we basically recompile everything that's on the
 Thomas> host, we'll to some extent loose this advantage.

True. It's a tradeoff ofcourse, but from looking at various bug
reports we're unfortunately not in a situation today where people can
just download BR on a random machine and run tar jxvf && make
menuconfig && make and expect it to work all the time.

Adding more dependencies on the host is not going to make this any

Bye, Peter Korsgaard

More information about the buildroot mailing list