From: James Newell <jnewell@wgate.com>
To: buildroot@busybox.net
Subject: [Buildroot] undefined __aeabi_read_tp
Date: Thu, 22 Feb 2007 15:58:52 -0500 [thread overview]
Message-ID: <1172177933.22966.13.camel@ndragon.eng.wgate.com> (raw)
I was building the ubuntu upstart package, and ran into an undefined
__aeabi_read_tp call.
The gcc defines:
-mtp=name
Specify the access model for the thread local storage pointer. The
valid models are soft, which generates calls to "__aeabi_read_tp",
cp15, which fetches the thread pointer from "cp15" directly (sup-
ported in the arm6k architecture), and auto, which uses the best
available method for the selected processor. The default setting
is auto.
The __aeabi_read_tp is not defined in the uclibc libs:
[jnewell at ndragon staging_dir]$ nm $(find . -type f -name "*.a")|grep
eabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
U __aeabi_read_tp
Does anyone know who should be defining this call?
Thanks,
Jim
Some of my config:
[jnewell at ndragon buildroot]$ grep -e ^BR2_GCC -e ABI -e THREAD .config
# BR2_ARM_OABI is not set
BR2_ARM_EABI=y
# BR2_PTHREADS_NONE is not set
# BR2_PTHREADS is not set
# BR2_PTHREADS_OLD is not set
BR2_PTHREADS_NATIVE=y
# BR2_PTHREAD_DEBUG is not set
BR2_GCC_VERSION_4_2=y
BR2_GCC_IS_SNAP=y
BR2_GCC_SNAP_DATE="20070214"
BR2_GCC_VERSION="4.2"
BR2_GCC_SHARED_LIBGCC=y
BR2_SOFT_FLOAT=y
next reply other threads:[~2007-02-22 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 20:58 James Newell [this message]
2007-02-22 21:15 ` [Buildroot] undefined __aeabi_read_tp James Newell
2007-03-07 14:47 ` Bernhard Fischer
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=1172177933.22966.13.camel@ndragon.eng.wgate.com \
--to=jnewell@wgate.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox