From: Steven J. Hill <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] NPTL support for uClibc-0.9.28
Date: Thu, 1 Nov 2007 12:40:06 -0500 [thread overview]
Message-ID: <20071101174006.GA9683@real.realitydiluted.com> (raw)
In-Reply-To: <297299.44939.qm@web7902.mail.in.yahoo.com>
> I am using buildroot to build cross toolchain for MIPS processor ( binutils 2.15, gcc 3.4.3, uClibc-0.9.28 and Linux 2.6.18 kernel) .
>
Nope. You will need gcc-4.2 or better and uClibc-0.9.29 from the
uClibc-NPTL branch in Subversion and binutils-2.17 or better.
> Can i get Native POSIX Threading (NPTL) support if i use above versions of binutils-2.15,gcc-3.4.3,uClibc-0.9.28 and Linux 2.6.18 kernel by enabling the "Enable Native POSIX Threading (NPTL) support?"
> in the buildroot Toolchain Options.
>
> Also does uClibc-0.9.28 support Native POSIX Threading (NPTL)?
>
No, and it never will.
> If not what are the suggested versions of binutils,uClibc and gcc to be used to get NPTL support for MIPS cross toolchain.
>
binutils-2.17.60.0.16
gcc-4.2.0
uClibc-NPTL
Honestly everyone, I am clearing my schedule to do the NPTL merge and
get SuperH, ARM and MIPS all with NPTL support into trunk.
-Steve
prev parent reply other threads:[~2007-11-01 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 10:46 [Buildroot] NPTL support for uClibc-0.9.28 sathesh babu
2007-11-01 17:40 ` Steven J. Hill [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=20071101174006.GA9683@real.realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox