From: Axel Lin <axel.lin@ingics.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why elf2flt is built *after* busybox
Date: Wed, 04 Sep 2013 00:20:50 +0800 [thread overview]
Message-ID: <1378225250.11000.4.camel@phoenix> (raw)
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
next reply other threads:[~2013-09-03 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 16:20 Axel Lin [this message]
2013-09-03 17:34 ` [Buildroot] Why elf2flt is built *after* busybox 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
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=1378225250.11000.4.camel@phoenix \
--to=axel.lin@ingics.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.