Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David J. Fiddes <D.J@fiddes.net>
To: buildroot@busybox.net
Subject: [Buildroot] ARM OABI build broken with current buildroot tip
Date: Mon, 18 Jul 2011 20:35:58 +0100	[thread overview]
Message-ID: <4E248B1E.1090904@fiddes.net> (raw)
In-Reply-To: <87fwm37vj4.fsf@macbook.be.48ers.dk>

Hi Peter,

> 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.

Ah. That's a bit of a show stopper.

> May I ask why you want to use a new C library / NPTL together with the
> obsolete OABI?

I have a very large multi-threaded C++ app and a custom embedded Linux 
platform that have historically been developed at different times. The 
SW is now over 10 years old and I fear change so just stuck to the ABI 
that has always worked...

Probably time to bite the bullet and move our kernel to EABI for our 
next major release.

thanks,

Dave

      reply	other threads:[~2011-07-18 19:35 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
2011-07-18 19:35   ` David J. Fiddes [this message]

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=4E248B1E.1090904@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