Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems compiling uclibc for Geode (i386)
Date: Wed, 29 Jun 2011 14:29:34 +0200	[thread overview]
Message-ID: <1309350574.17457.5.camel@sven> (raw)
In-Reply-To: <1309291371.21632.5.camel@bender>

On Tue, 2011-06-28 at 22:02 +0200, Sven Neumann wrote:
> Hi,
> 
> I am currently trying to update our buildroot system to the latest
> version that I pulled from your git repository yesterday. Things work
> reasonably well and I have everything compiling fine for the ARM
> platform. The Geode platform however is causing trouble when it comes to
> compiling uclibc 0.9.32.
> 
> First I had to fix a compile problem by pulling in this patch from the
> uclibc repository:
> http://git.uclibc.org/uClibc/patch/?id=8245f3b4638fdff2011c2657af1bb211def704bc
> 
> 
> But now I am stuck with this linker error:
> 
>   LD libuClibc-0.9.32.so
> libc/libc_so.a(err.os):(.text.vwarn_work+0x127): undefined reference to
> `__lll_unlock_wake_private'
> collect2: ld returned 1 exit status
> make[1]: *** [lib/libc.so] Error 1
> make[1]: Leaving directory
> `/home/sven/git/buildroot/output/toolchain/uClibc-0.9.32'

Looks like NPTL support is broken for the generic 386 target. I've
changed the uclibc configuration to i586 now (in the hope that this will
work for a Geode processor) and that has fixed above problem for me.


Sven

  reply	other threads:[~2011-06-29 12:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 20:02 [Buildroot] problems compiling uclibc for Geode (i386) Sven Neumann
2011-06-29 12:29 ` Sven Neumann [this message]
2011-06-29 13:54   ` Michael S. Zick
2011-06-29 14:43   ` Thomas Petazzoni
     [not found]     ` <4E0B3B3D.3090108@in-2-technology.co.uk>
2011-06-29 14:55       ` Thomas Petazzoni
2011-07-05  7:00         ` Peter Korsgaard
2011-07-05  7:17           ` Thomas Petazzoni
2011-06-29 16:14     ` Yann E. MORIN
2011-06-29 18:36     ` Khem Raj
2011-07-05  6:58   ` Peter Korsgaard

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=1309350574.17457.5.camel@sven \
    --to=s.neumann@raumfeld.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