From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Add support for uclibc NPTL toolchain.
Date: Thu, 29 Jul 2010 17:36:21 +0200 [thread overview]
Message-ID: <877hkee1vu.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1280301099-5930-1-git-send-email-raj.khem@gmail.com> (Khem Raj's message of "Wed, 28 Jul 2010 00:11:36 -0700")
>>>>> "Khem" == Khem Raj <raj.khem@gmail.com> writes:
Khem> Hi
Khem> The following set of patches is a revised list of nptl build
Khem> sequence support in BR internal toolchain.
Thanks, committed. I decided to simply drop the old 0.9.28.3 version
instead of applying patch 2 though.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-07-29 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 7:11 [Buildroot] [PATCH 0/3] Add support for uclibc NPTL toolchain Khem Raj
2010-07-28 7:11 ` [Buildroot] [PATCH 1/3] " Khem Raj
2010-07-28 7:11 ` [Buildroot] [PATCH 2/3] uclibc.mk: Make all available versions of uclibc compilable with new toolchain build sequence Khem Raj
2010-07-28 7:11 ` [Buildroot] [PATCH 3/3] gcc-4.2.4: Add patch to accept --with-abi=aapcs-linux Khem Raj
2010-07-29 15:36 ` Peter Korsgaard [this message]
2010-07-29 17:02 ` [Buildroot] [PATCH 0/3] Add support for uclibc NPTL toolchain Khem Raj
2010-07-29 19:10 ` Peter Korsgaard
2010-07-30 2:12 ` Khem Raj
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=877hkee1vu.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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