Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominic Newton <dominic.newton@in-2-technology.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling problem with NPTL threads on x86
Date: Thu, 23 Jun 2011 18:49:13 +0100	[thread overview]
Message-ID: <4E037C99.2030308@in-2-technology.co.uk> (raw)

Hi,

I'm fairly new to buildroot and have run into a problem that I have 
partially fixed - but I could use a few pointers.

I've built several systems using buildroot that run perfectly OK. 
However I would like to use NPTL library rather than linuxthreads.

I've had the same problem with buildroot-2011.02 and .05 using the 
recent rc2 and rc3 of uclibc0.9....

Compiling with NPTL throws up some errors involving 'pthread.h not 
found/does not exist'. I've compiled a linuxthreads version OK.

A bit of digging has found that while linuxthreads puts pthread.h, 
semaphore.h and bits/ptheadtypes.h into the include directories, when 
configuring NPTL, they get forgotten. The uclibc libpthread/nptl has 
semaphore.h and pthread.h, but no pthreadtypes. I symlinked them into 
the the include directory in the output/toolchain/uclicbc... and the 
output/host/usr.....sysroot directories and this seems to have cludged 
it together (using pthreadtypes from linuxthreads).

So I think I'm on the right track. My question is where do I find the 
script/makefile(s) that unpacks the uclibc archive, parses the buildroot 
config and attempts to create the includes. I'd like to make sure the 
appropriate files are copied over in as amny cases as possible.

Any help gratefull received, once properly sorted I'll feed it back in - 
assuming I'm not doing something idiotic or a fix already exists.

-- 
Dominic Newton

             reply	other threads:[~2011-06-23 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 17:49 Dominic Newton [this message]
2011-06-24 17:46 ` [Buildroot] Compiling problem with NPTL threads on x86 Dominic Newton
2011-07-06  5:19   ` 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=4E037C99.2030308@in-2-technology.co.uk \
    --to=dominic.newton@in-2-technology.co.uk \
    --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