Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Compiling problem with NPTL threads on x86
@ 2011-06-23 17:49 Dominic Newton
  2011-06-24 17:46 ` Dominic Newton
  0 siblings, 1 reply; 3+ messages in thread
From: Dominic Newton @ 2011-06-23 17:49 UTC (permalink / raw)
  To: buildroot

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Compiling problem with NPTL threads on x86
  2011-06-23 17:49 [Buildroot] Compiling problem with NPTL threads on x86 Dominic Newton
@ 2011-06-24 17:46 ` Dominic Newton
  2011-07-06  5:19   ` Peter Korsgaard
  0 siblings, 1 reply; 3+ messages in thread
From: Dominic Newton @ 2011-06-24 17:46 UTC (permalink / raw)
  To: buildroot

OK problem looks more or less solved.

NPTL threads are mainly supported by the latest uclibc release, but the 
devil is in the detail. Some target architecture variants are not 
supported. The buildroot menuconfig may show that NPTL threads are 
available as an options, but when uclibc is configured the local logic 
throws this out. A good check is to run uclibc-menuconfig and test out 
the options on that.

So with this proviso I have compiled s basic system for a couple of 
platforms with all thread variants and have tested each one - they work !

Dominic Newton

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Compiling problem with NPTL threads on x86
  2011-06-24 17:46 ` Dominic Newton
@ 2011-07-06  5:19   ` Peter Korsgaard
  0 siblings, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2011-07-06  5:19 UTC (permalink / raw)
  To: buildroot

>>>>> "Dominic" == Dominic Newton <dominic.newton@in-2-technology.co.uk> writes:

 Dominic> OK problem looks more or less solved.
 Dominic> NPTL threads are mainly supported by the latest uclibc release, but
 Dominic> the devil is in the detail. Some target architecture variants are not
 Dominic> supported. The buildroot menuconfig may show that NPTL threads are
 Dominic> available as an options, but when uclibc is configured the local logic
 Dominic> throws this out. A good check is to run uclibc-menuconfig and test out
 Dominic> the options on that.

What configurations are those? Perhaps we can improve the menuconfig
logic in buildroot.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-07-06  5:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-23 17:49 [Buildroot] Compiling problem with NPTL threads on x86 Dominic Newton
2011-06-24 17:46 ` Dominic Newton
2011-07-06  5:19   ` Peter Korsgaard

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox