[Buildroot] Why elf2flt is built *after* busybox

Thomas De Schampheleire patrickdepinguin+buildroot at gmail.com
Wed Sep 4 06:50:10 UTC 2013


Hi Axel,

Op 4-sep.-2013 04:04 schreef "Axel Lin" <axel.lin at ingics.com> het volgende:
>
> > This time my question is: Is it normal elf2flt is built *after* busybox?
> > (This looks like a new founding to me)
> > I know elf2ft is broken.
> > I'm just not sure if the build order is one of the root cause to make
> > elf2flt broken.
> > I ask the question because I'm not familiar with buiildroot now, I even
> > don't know how to specify package build order.
> > (In this case, move elf2flt build ealier than busybox.)
> > So I expect someone can answer the question on mailing list.
> Hi,
> I test build for blackfin with BR2_PACKAGE_HOST_ELF2FLT=y.
> The first time build result in a ELF 32-bit LSB executable.
> (I think it is because busybox is built *before* elf2flt.)
> However, I build busybox again with "make busybox-rebuild" and
> then I got a BFLT executable.
> So now I do think the build order for elf2flt does matter.

The build order of packages is in general to be considered random. However,
if some packages need to be built before others, this should be expressed
in the FOO_DEPENDENCIES variable. If FOO_DEPENDENCIES = bar, then package
bar will be built before package FOO.

Some packages need to be built before _all_ other packages, they are global
dependencies. For this, there is the support/dependencies infrastructure.

Some packages are also built before the real target packages as part of the
toolchain building/extracting.

Possibly, elf2flt can be added to the last category, or to the
support/dependencies one.

Best regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130904/78618709/attachment.html>


More information about the buildroot mailing list