From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Sasha Sirotkin <buildroot@browserseal.com>
Subject: Re: eglibc issue with TLS
Date: Wed, 31 Mar 2010 16:08:00 -0000 [thread overview]
Message-ID: <201003311757.36313.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4BB36A06.8010008@browserseal.com>
Sasha, All,
On Wednesday 31 March 2010 172806 Sasha Sirotkin wrote:
> When I try to compile crosstool-ng with eglibc and nptl I get the
> following error message:
>
> [ALL ] In file included from ../include/tls.h:6,
> [ALL ] from ../include/link.h:45,
> [ALL ] from ../include/dlfcn.h:3,
> [ALL ] from ../sysdeps/generic/ldsodefs.h:32,
> [ALL ] from
> ../eglibc-ports-2_10/sysdeps/arm/ldsodefs.h:39,
> [ALL ] from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
> [ALL ] from <stdin>:2:
> [ERROR] ../eglibc-ports-2_10/sysdeps/arm/nptl/tls.h:48:3: error:
> #error "TLS support is required."
> [ALL ] In file included from ../include/tls.h:6,
> [ALL ] from
> ../eglibc-ports-2_10/sysdeps/unix/sysv/linux/arm/sysdep.h:31,
> [ALL ] from
> ../eglibc-ports-2_10/sysdeps/unix/sysv/linux/arm/eabi/sysdep.h:26,
> [ALL ] from <stdin>:1:
> [ERROR] ../eglibc-ports-2_10/sysdeps/arm/nptl/tls.h:48:3: error:
> #error "TLS support is required."
> [ALL ] In file included from
> ../eglibc-ports-2_10/sysdeps/arm/nptl/tls.h:57,
> [ALL ] from ../include/tls.h:6,
> [ALL ] from ../include/link.h:45,
> [ALL ] from ../include/dlfcn.h:3,
> [ALL ] from ../sysdeps/generic/ldsodefs.h:32,
> [ALL ] from
> ../eglibc-ports-2_10/sysdeps/arm/ldsodefs.h:39,
> [ALL ] from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
> [ALL ] from <stdin>:2:
> [ERROR]
> ../eglibc-ports-2_10/sysdeps/unix/sysv/linux/arm/eabi/sysdep.h:31:3:
> error: #error Kernel headers are too old
> [ALL ] In file included from <stdin>:1:
> [ERROR]
> ../eglibc-ports-2_10/sysdeps/unix/sysv/linux/arm/eabi/sysdep.h:31:3:
> error: #error Kernel headers are too old
^^^^^^^^^^^^^^^^^^^^^^^^^^
I think this is quite relevant...
For NPTL on ARM, EABI is required, and EABI requires is 2.6.16.
What's your .config? Do you use specific kernel headers?
Also, i would suggest that you start off an existing sample that are bundled
with crosstool-NG, and are known to (at least!) build properly:
# ct-ng list-samples
[--SNIP--]
arm-unknown-linux-gnueabi
arm-unknown-linux-uclibcgnueabi
[--SNIP--]
# ct-ng arm-unknown-linux-gnueabi
# ct-ng menuconfig (review the configuration and paths)
# ct-ng build
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2010-03-31 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 15:28 Sasha Sirotkin
2010-03-31 16:08 ` Yann E. MORIN [this message]
2010-03-31 18:01 ` Alexander (Sasha) Sirotkin
2010-03-31 21:54 ` Yann E. MORIN
2010-04-01 7:48 ` Sasha Sirotkin
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=201003311757.36313.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=buildroot@browserseal.com \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).