* [Buildroot] Why elf2flt is built *after* busybox
@ 2013-09-03 16:20 Axel Lin
2013-09-03 17:34 ` Thomas Petazzoni
0 siblings, 1 reply; 6+ messages in thread
From: Axel Lin @ 2013-09-03 16:20 UTC (permalink / raw)
To: buildroot
Hi,
Just enable elf2flt and start build.
From the build log I found the build system build busybox before elf2flt.
Is this normal?
I thought elf2flt needs to be ready before building other packages?
Below shows my package build order:
$ grep "_installed" mylog
touch /opt/test/buildroot/buildroot/output/build/host-binutils-2.21.1/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-m4-1.4.16/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-gmp-5.1.2/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-mpfr-3.1.2/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-libtool-2.4.2/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-autoconf-2.69/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-automake-1.11.6/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-mpc-1.0.1/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-gcc-initial-4.5.4/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/linux-headers-3.10.10/.stamp_staging_installed
touch /opt/test/buildroot/buildroot/output/build/linux-headers-3.10.10/.stamp_target_installed
touch /opt/test/buildroot/buildroot/output/build/host-gcc-intermediate-4.5.4/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/uclibc-0.9.33.2/.stamp_staging_installed
touch /opt/test/buildroot/buildroot/output/build/uclibc-0.9.33.2/.stamp_target_installed
touch /opt/test/buildroot/buildroot/output/build/host-gcc-final-4.5.4/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/busybox-1.21.1/.stamp_target_installed
touch /opt/test/buildroot/buildroot/output/build/host-pkgconf-0.8.9/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-e2fsprogs-1.42.8/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-zlib-1.2.8/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-elf2flt-cvs/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-genext2fs-1.4.1/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-fakeroot-1.18.2/.stamp_host_installed
touch /opt/test/buildroot/buildroot/output/build/host-makedevs-undefined/.stamp_host_installed
Just not sure if it is related to the message shows in the end of
output/build/busybox-1.21.1/busybox_unstripped.out:
(looks like ld does not recognize -elf2flt )
/opt/test/buildroot/buildroot/output/host/usr/lib/gcc/arm-buildroot-uclinux-uclibcgnueabi/4.5.4/../../../../arm-buildroot-uclinux-uclibcgnueabi/bin/ld: warning: cannot find entry symbol lf2flt=-s65535; defaulting to 00000000000080ac
Regards,
Axel
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Why elf2flt is built *after* busybox
2013-09-03 16:20 [Buildroot] Why elf2flt is built *after* busybox Axel Lin
@ 2013-09-03 17:34 ` Thomas Petazzoni
2013-09-03 23:57 ` Axel Lin
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Petazzoni @ 2013-09-03 17:34 UTC (permalink / raw)
To: buildroot
Dear Axel Lin,
On Wed, 04 Sep 2013 00:20:50 +0800, Axel Lin wrote:
> Just enable elf2flt and start build.
> From the build log I found the build system build busybox before
> elf2flt. Is this normal?
> I thought elf2flt needs to be ready before building other packages?
Because elf2flt support is broken and someone needs to fix it. You've
already sent several e-mails about this. Gustavo Zacarias is working on
improving the elf2flt, but on a spare time basis, so it's progressing
as time and motivation permits.
Sorry to be a bit rude, but if you want things to move forward faster,
either send patches to fix the problems and get the thing working, or
hire someone to do this work for you. I'm sure ARM noMMU support in
Buildroot will improve, because there are more and more Cortex-M
systems that are capable of running Linux, but it's not something that
is currently well supported in Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Why elf2flt is built *after* busybox
2013-09-03 17:34 ` Thomas Petazzoni
@ 2013-09-03 23:57 ` Axel Lin
2013-09-04 2:04 ` Axel Lin
2013-09-04 7:48 ` Thomas Petazzoni
0 siblings, 2 replies; 6+ messages in thread
From: Axel Lin @ 2013-09-03 23:57 UTC (permalink / raw)
To: buildroot
2013/9/4 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> Dear Axel Lin,
>
> On Wed, 04 Sep 2013 00:20:50 +0800, Axel Lin wrote:
>
>> Just enable elf2flt and start build.
>> From the build log I found the build system build busybox before
>> elf2flt. Is this normal?
>> I thought elf2flt needs to be ready before building other packages?
>
> Because elf2flt support is broken and someone needs to fix it. You've
> already sent several e-mails about this. Gustavo Zacarias is working on
> improving the elf2flt, but on a spare time basis, so it's progressing
> as time and motivation permits.
>
> Sorry to be a bit rude, but if you want things to move forward faster,
> either send patches to fix the problems and get the thing working, or
> hire someone to do this work for you. I'm sure ARM noMMU support in
> Buildroot will improve, because there are more and more Cortex-M
> systems that are capable of running Linux, but it's not something that
> is currently well supported in Buildroot.
Hi Thomas,
I think you totally missed my point.
I ask the question because I try to figure out the issue I found.
I ask the question because I'm leaning using buildroot.
It's good to know someone is working on this issue, however I didn't
mean to push someone to work for me. That is not my intention.
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.
Note, I'll send patch if I'm pretty sure I have fixed some issue.
But at this moment I just try to dig out the problem.
Regards,
Axel
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Why elf2flt is built *after* busybox
2013-09-03 23:57 ` Axel Lin
@ 2013-09-04 2:04 ` Axel Lin
2013-09-04 6:50 ` Thomas De Schampheleire
2013-09-04 7:48 ` Thomas Petazzoni
1 sibling, 1 reply; 6+ messages in thread
From: Axel Lin @ 2013-09-04 2:04 UTC (permalink / raw)
To: buildroot
> 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.
Regards,
Axel
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Why elf2flt is built *after* busybox
2013-09-04 2:04 ` Axel Lin
@ 2013-09-04 6:50 ` Thomas De Schampheleire
0 siblings, 0 replies; 6+ messages in thread
From: Thomas De Schampheleire @ 2013-09-04 6:50 UTC (permalink / raw)
To: buildroot
Hi Axel,
Op 4-sep.-2013 04:04 schreef "Axel Lin" <axel.lin@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>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Why elf2flt is built *after* busybox
2013-09-03 23:57 ` Axel Lin
2013-09-04 2:04 ` Axel Lin
@ 2013-09-04 7:48 ` Thomas Petazzoni
1 sibling, 0 replies; 6+ messages in thread
From: Thomas Petazzoni @ 2013-09-04 7:48 UTC (permalink / raw)
To: buildroot
Dear Axel Lin,
On Wed, 4 Sep 2013 07:57:12 +0800, Axel Lin wrote:
> >> Just enable elf2flt and start build.
> >> From the build log I found the build system build busybox before
> >> elf2flt. Is this normal?
> >> I thought elf2flt needs to be ready before building other packages?
> >
> > Because elf2flt support is broken and someone needs to fix it.
> > You've already sent several e-mails about this. Gustavo Zacarias is
> > working on improving the elf2flt, but on a spare time basis, so
> > it's progressing as time and motivation permits.
> >
> > Sorry to be a bit rude, but if you want things to move forward
> > faster, either send patches to fix the problems and get the thing
> > working, or hire someone to do this work for you. I'm sure ARM
> > noMMU support in Buildroot will improve, because there are more and
> > more Cortex-M systems that are capable of running Linux, but it's
> > not something that is currently well supported in Buildroot.
>
> Hi Thomas,
>
> I think you totally missed my point.
> I ask the question because I try to figure out the issue I found.
> I ask the question because I'm leaning using buildroot.
> It's good to know someone is working on this issue, however I didn't
> mean to push someone to work for me. That is not my intention.
The thing is that you've been posting constantly error reports about
the elf2flt support, while we have kept telling you from the beginning
that it is not well supported by Buildroot today. So keeping sending
error reports is kind of useless: at this point, someone needs to look
at the problem and fix it. I know Gustavo has started working on this,
but I believe ARM noMMU support is not his priority. If it has a higher
priority for someone else, then that someone else should work on it and
fix the issues. Constantly posting error reports will not make the
thing progress faster.
> This time my question is: Is it normal elf2flt is built *after*
> busybox? (This looks like a new founding to me)
No, this is not normal.
> I ask the question because I'm not familiar with buiildroot now, I
> even don't know how to specify package build order.
By putting the relevant dependency name in <pkg>_DEPENDENCIES, as
explained in the Buildroot documentation,
http://buildroot.org/downloads/manual/manual.html.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-09-04 7:48 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-03 16:20 [Buildroot] Why elf2flt is built *after* busybox Axel Lin
2013-09-03 17:34 ` Thomas Petazzoni
2013-09-03 23:57 ` Axel Lin
2013-09-04 2:04 ` Axel Lin
2013-09-04 6:50 ` Thomas De Schampheleire
2013-09-04 7:48 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox