From: Finn Thain <fthain@telegraphics.com.au>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: eglibc sysroot
Date: Thu, 14 Oct 2010 23:11:55 +1100 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1010142255020.276@localhost> (raw)
In-Reply-To: <Pine.BSM.4.64L.1010141131490.16747@herc.mirbsd.org>
On Thu, 14 Oct 2010, Thorsten Glaser wrote:
>
> Is there a simple TLS test programme I can run before extracting the
> eglibc sysroot and building gcc, to see whether the Linux kernel is
> working as expected?
I don't know of any. Under the NPTL sysroot, you should see this:
$ /lib/libc.so.6
...
Available extensions:
...
Native POSIX Threads Library by Ulrich Drepper et al
[snip]
> extract sysroot
> install updated linux-headers-*.deb and friends over that
You might want to remove the linux-2.6_2.6.32-23 kernel headers already in
the sysroot first. (They are courtesy of make headers_install and worked
fine for my purposes but I don't know how they differ from the
linux-headers deb.)
Or you could just use the existing headers instead of the linux-headers
deb until you get the eglibc packages built, at which point you can ditch
the sysroot and debootstrap.
Finn
prev parent reply other threads:[~2010-10-14 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1009221445130.7495@nippy.intranet>
[not found] ` <alpine.OSX.2.00.1010122347280.278@localhost>
[not found] ` <Pine.BSM.4.64L.1010121755580.28735@herc.mirbsd.org>
[not found] ` <alpine.OSX.2.00.1010131102470.285@localhost>
2010-10-13 16:59 ` eglibc sysroot Thorsten Glaser
2010-10-14 11:36 ` Thorsten Glaser
2010-10-14 12:11 ` Finn Thain [this message]
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=alpine.OSX.2.00.1010142255020.276@localhost \
--to=fthain@telegraphics.com.au \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.