From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARM OABI build broken with current buildroot tip
Date: Mon, 18 Jul 2011 12:06:23 +0200 [thread overview]
Message-ID: <87fwm37vj4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4E22BFA1.7080800@fiddes.net> (David J. Fiddes's message of "Sun, 17 Jul 2011 11:55:29 +0100")
>>>>> "David" == David J Fiddes <D.J@fiddes.net> writes:
David> Hi,
David> I'm trying to build an up to date ARM OABI toolchain with uClibc
David> 0.9.32. The build fails with a missing stack unwind symobl.
David> The toolchain I'm trying to configure is pretty straight forward. From
David> a "make distclean" I configure:
David> - ARM processor
David> - OABI
David> - Disable busybox and filesystem image generation
David> Switching uClibc to 0.9.31 allows the build to succeed.
The problem is NPTL threading support. A quick look in
libpthread/nptl/sysdeps/arm shows a number of EABI references. It seems
like NPTL on ARM is only supported with EABI.
And indeed, OABI / uClibc 0.9.32 / linuxthreads-old builds fine.
I'll adjust Buildroot so you cannot select NTPL together with OABI.
David> It seems like this is a uClibc bug but I'm not sure how best to
David> separate the toolchain build form the uClibc build.
It looks pretty independent of anything Buildroot related. You are
welcome to ask them regarding non-EABI NPTL support, but I would imagine
that such an uncommon configuration has fairly low priority.
May I ask why you want to use a new C library / NPTL together with the
obsolete OABI?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-18 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:55 [Buildroot] ARM OABI build broken with current buildroot tip David J. Fiddes
2011-07-18 10:06 ` Peter Korsgaard [this message]
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=87fwm37vj4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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