From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 859] New: Add (head of) nptl branch to list of uClibc versions
Date: Tue, 12 Jan 2010 09:20:18 +0000 (UTC) [thread overview]
Message-ID: <bug-859-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=859
Summary: Add (head of) nptl branch to list of uClibc versions
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: jpihl at nevion.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Please add an option to use a snapshot of the NPTL branch of uClibc. That would
enable NPTL for the platforms that actually support it (ARM among others).
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-01-12 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 9:20 bugzilla at busybox.net [this message]
2010-02-21 22:33 ` [Buildroot] [Bug 859] Add (head of) nptl branch to list of uClibc versions bugzilla at busybox.net
2010-07-28 14:07 ` bugzilla at busybox.net
2010-07-29 19:59 ` bugzilla at busybox.net
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=bug-859-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.