From: "Jan Kundrát" <jan.kundrat@fzu.cz>
To: Jerome Brown <jerome@concepts.net.nz>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Re: Xen and reiser4
Date: Wed, 12 Jan 2005 23:00:38 +0100 [thread overview]
Message-ID: <41E59E06.7040507@fzu.cz> (raw)
In-Reply-To: <41E583F6.2010201@concepts.net.nz>
Jerome Brown wrote:
>>> That's the exactly the thing which I didn't want to do, I want to
>>> build glibc with linuxthreads and nptl
>>
>>
>> Look at your $PORTDIR/sys-libs/glibc/glibc-<version>.ebuild, locate
>> want_tls function and add "return 1" as the first line of the
>> function. This is ugly hack, but should work (not tested).
>> Disadvantage is that it won't survive `emerge sync`, but you can add
>> it into $PORTDIR_OVERLAY...
>
>
> If you compile glibc with the nptl USE flag it will compile both NTPL
> and LinuxThreads into glibc. If you have specified the ntplonly USE flag
> then it will not compile LinuxThreads. Check to see if you have the
> nptlonly flag defined (most of the tutorials I remember looking at say
> to define it). If so, remove it and recompile glibc. You shouldn't need
> to recompile anything else, as the nptlonly USE flag only applys to
> glibc, so everything else should work fine from there.
If I'm not mistaken, NPTL (Native POSIX Thread Library) is a replecement
of LinuxThreads, threads implementation library used as default under
pre-2.6 kernels. TLS (Thread Local Storage) is AFAIK something else (at
least I think so because Ming wants to have NPTL enabled but TLS disabled).
I've created gentoo bugreport - http://bugs.gentoo.org/show_bug.cgi?id=77678
-jkt
--
cd /local/pub && more beer > /dev/mouth
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-12 22:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41C08801.4060908@spaceball.cjb.net>
2004-12-15 18:56 ` Xen and reiser4 Ming-Wei Shih
2004-12-17 19:17 ` Ming-Wei Shih
2005-01-11 20:12 ` Ming-Wei Shih
2005-01-11 21:23 ` Jan Kundrát
2005-01-11 23:37 ` Ming-Wei Shih
2005-01-12 14:26 ` Jan Kundrát
2005-01-12 19:00 ` Ming-Wei Shih
2005-01-12 20:09 ` Jerome Brown
2005-01-12 21:14 ` nfsroot and brige Adam Sulmicki
2005-01-12 21:44 ` double free Adam Sulmicki
2005-01-12 22:04 ` Keir Fraser
2005-01-12 22:32 ` Adam Sulmicki
2005-01-12 22:31 ` Keir Fraser
2005-01-12 22:57 ` Adam Sulmicki
2005-01-17 7:56 ` nfsroot and brige Adam Sulmicki
2005-01-12 22:00 ` Jan Kundrát [this message]
2005-01-12 23:09 ` Re: Xen and reiser4 Jerome Brown
2005-01-13 13:43 ` Jan Kundrát
2005-01-17 15:22 ` Jan Kundrát
2005-01-11 22:28 ` Mark A. Williamson
2005-01-12 8:09 ` Ming-Wei Shih
2005-01-12 14:16 ` Jan Kundrát
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=41E59E06.7040507@fzu.cz \
--to=jan.kundrat@fzu.cz \
--cc=jerome@concepts.net.nz \
--cc=xen-devel@lists.sourceforge.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 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.