From: David J. Fiddes <D.J@fiddes.net>
To: buildroot@busybox.net
Subject: [Buildroot] ARM OABI build broken with current buildroot tip
Date: Sun, 17 Jul 2011 11:55:29 +0100 [thread overview]
Message-ID: <4E22BFA1.7080800@fiddes.net> (raw)
Hi,
I'm trying to build an up to date ARM OABI toolchain with uClibc 0.9.32.
The build fails with a missing stack unwind symobl.
The toolchain I'm trying to configure is pretty straight forward. From a
"make distclean" I configure:
- ARM processor
- OABI
- Disable busybox and filesystem image generation
Switching uClibc to 0.9.31 allows the build to succeed.
I'm using buildroot: bef98b7c10a9969bc3f8b977dd9e0bdafba684a3
The build error is:
/usr/bin/make -j1 -C
/home/dave/source/cvs-versions/buildroot/output/toolchain/uClibc-0.9.32 \
ARCH="arm" \
PREFIX=/home/dave/source/cvs-versions/buildroot/output/host/usr/arm-unknown-linux-uclibc/sysroot \
DEVEL_PREFIX=/usr/ \
RUNTIME_PREFIX=/ \
install_runtime install_dev
make[1]: Entering directory
`/home/dave/source/cvs-versions/buildroot/output/toolchain/uClibc-0.9.32'
LD libuClibc-0.9.32.so
libc/libc_so.a(close.oS):(.ARM.exidx+0x0): undefined reference to
`__aeabi_unwind_cpp_pr0'
collect2: ld returned 1 exit status
make[1]: *** [lib/libc.so] Error 1
make[1]: Leaving directory
`/home/dave/source/cvs-versions/buildroot/output/toolchain/uClibc-0.9.32'
make: ***
[/home/dave/source/cvs-versions/buildroot/output/host/usr/arm-unknown-linux-uclibc/sysroot/usr/lib/libc.a]
Error 2
It seems like this is a uClibc bug but I'm not sure how best to separate
the toolchain build form the uClibc build.
Dave
next reply other threads:[~2011-07-17 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:55 David J. Fiddes [this message]
2011-07-18 10:06 ` [Buildroot] ARM OABI build broken with current buildroot tip Peter Korsgaard
2011-07-18 19:35 ` David J. Fiddes
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=4E22BFA1.7080800@fiddes.net \
--to=d.j@fiddes.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox