Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] nios2 and TLS
@ 2007-06-18  8:53 Johan Thelin
  2007-06-21  3:45 ` Steven J. Hill
  0 siblings, 1 reply; 2+ messages in thread
From: Johan Thelin @ 2007-06-18  8:53 UTC (permalink / raw)
  To: buildroot

Hi all,

I've been spending some time now trying to use buildroot to build a
working toolchain and root for nios2. My requirements include C++
support and threading support.

My problem is that I keep getting stuck on the TLS stuff. The error
message goes something like:

  In file included from ./include/errno.h:62,
                 from libm/k_standard.c:19:
  ./include/bits/uClibc_errno.h:14:18: tls.h: No such file or directory

Removing the need for TLS in the libm only means postponing the error
messages from hell to the libpthread build. As I understand it, this
is inevitable as TLS handles the thread-local storage of variables.

After having studied mailing archived and googled around I've found
two traces of hope:

  #1 The "TLS stuff" seems to be optional. Is it possible to build a
toolchain supporting C++ and threading without it?

  #2 Finding the mystery patch that solves this. I see hints of
Microtronix having a solution that can be found. I just don't know
where to look.


Best regards,

Johan Thelin

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

* [Buildroot] nios2 and TLS
  2007-06-18  8:53 [Buildroot] nios2 and TLS Johan Thelin
@ 2007-06-21  3:45 ` Steven J. Hill
  0 siblings, 0 replies; 2+ messages in thread
From: Steven J. Hill @ 2007-06-21  3:45 UTC (permalink / raw)
  To: buildroot

You need to NOT select NPTL threading.

-Steve

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

end of thread, other threads:[~2007-06-21  3:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-18  8:53 [Buildroot] nios2 and TLS Johan Thelin
2007-06-21  3:45 ` Steven J. Hill

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