From: Tor Krill <tor@krill.nu>
To: buildroot@busybox.net
Subject: [Buildroot] Error building arm toolchain: undefined reference to `raise'
Date: Thu, 26 Oct 2006 11:45:09 +0200 [thread overview]
Message-ID: <1161855909.454083a599a48@edna.homeip.net> (raw)
Hi,
I'm trying to build an up to date toolchain for our arm920t board, at91rm9200.
However compilation fails with a:
/home/tor/tmp/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-ld -EL -e
_start -z now -Bsymbolic -shared --warn-common --export-dynamic --sort-common
-z combreloc --discard-locals --discard-all --no-undefined -s
-soname=ld-uClibc.so.0 \
-o ld-uClibc-0.9.28.so arm/resolve.o ldso.o
/home/tor/tmp/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibc/4.1.1/libgcc.a
/home/tor/tmp/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibc/4.1.1/libgcc.a(_dvmd_lnx.o):
In function `__div0':
/home/tor/tmp/buildroot/toolchain_build_arm/gcc-4.1.1/gcc/config/arm/lib1funcs.asm:1000:
undefined reference to `raise'
make[3]: *** [ld-uClibc-0.9.28.so] Error 1
make[3]: Leaving directory
`/home/tor/tmp/buildroot/toolchain_build_arm/uClibc-0.9.28/ldso/ldso'
make[2]: *** [ldso] Error 2
make[2]: Leaving directory
`/home/tor/tmp/buildroot/toolchain_build_arm/uClibc-0.9.28/ldso'
make[1]: *** [_dir_ldso] Error 2
make[1]: Leaving directory
`/home/tor/tmp/buildroot/toolchain_build_arm/uClibc-0.9.28'
I used latest possible stable versions,
* gcc-4.1.1
* Kernel headers 2.6.12
* Binutils 2.17
* no softfloat
* Busybox snapshot
* Default stable uClibc 0.9.28
Am i missing something here?
Regards
/Tor
next reply other threads:[~2006-10-26 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:45 Tor Krill [this message]
2006-10-26 19:26 ` [Buildroot] Error building arm toolchain: undefined reference to `raise' Philippe Ney
2006-10-27 6:06 ` Tor Krill
2006-10-27 8:22 ` Michael Opdenacker
2006-11-01 11:53 ` MikeW
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 17:48 Michael Opdenacker
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=1161855909.454083a599a48@edna.homeip.net \
--to=tor@krill.nu \
--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