From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] (fwd) RFC PATCH [wbx@uclibc-ng.org]
Date: Mon, 19 Sep 2016 15:06:31 +0200 [thread overview]
Message-ID: <20160919130631.GH7322@waldemar-brodkorb.de> (raw)
----- Forwarded message from Waldemar Brodkorb <wbx@uclibc-ng.org> -----
Date: Mon, 19 Sep 2016 14:41:49 +0200
From: Waldemar Brodkorb <wbx@uclibc-ng.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
To: devel at uclibc-ng.org
Cc: Max Filippov <jcmvbkbc@gmail.com>, Alexey Brodkin <Alexey.Brodkin@synopsys.com>, Vineet Gupta <Vineet.Gupta1@synopsys.com>, Vincent Ren-Wei Chen <vincentc@andestech.com>,
Che-Wei Chuang <cnoize@andestech.com>, buildroot at buildroot.org
Subject: RFC PATCH
Hi,
I would like to suggest following patch to have a single libc
library. This would solve a lot of problems in buildroot and other
buildsystems.
I would love to make a release at the end of this month.
What do you think about it?
For buildroot people, here is a patch for testing:
http://debug.openadk.org/buildroot/0001-experimental-uClibc-ng-patches.patch
This will solve a lot of old autobuild failures, f.e. the libarchive
static stuff.
I worked for many hours on this, so don't be too harsh with your
feedback ;)
Thanks in advance!
Waldemar
P.s.: I know it is a big patch, but I see no good chances to split
it in pieces.
reply other threads:[~2016-09-19 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160919130631.GH7322@waldemar-brodkorb.de \
--to=wbx@openadk.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