All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Draszik" <git@andred.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] musl/glibc/binutils updates
Date: Wed, 13 Jul 2016 11:14:32 +0100	[thread overview]
Message-ID: <1468404872.23527.7.camel@andred.net> (raw)
In-Reply-To: <aa5165d3-c97f-3a37-73b3-31cd5cc704e9@linux.intel.com>

On Fr, 2016-07-08 at 17:19 +0300, Alexander Kanavin wrote:
> On 07/08/2016 05:07 PM, Khem Raj wrote:
> > > > Fix gcc5 hang in SDK with -mmusl
> > > > Update musl to 1.1.15 release
> > > > Update binutils to 2.26.1
> > > > Update glibc to latest on 2.24 freeze tree
> > > 
> > > 
> > > What about uclibc? It should be updated as well.
> > 
> > I do not test it regularly. If there are users who want it we can
> > continue
> 
> Maybe we should reassign the recipes to André Draszik then?

Thanks for thinking of me :-) I do have a plan to move away from uClibc as
well, though.

Ross, so if consensus is to remove it from OE, I don't really have a problem
with that.


Cheers,
Andre'



  reply	other threads:[~2016-07-13 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 18:08 [PATCH 0/4] musl/glibc/binutils updates Khem Raj
2016-07-07 18:08 ` [PATCH 1/4] gcc-5.4: Fix hang with mmusl option on cmdline Khem Raj
2016-07-07 18:08 ` [PATCH 2/4] glibc: Upgrade to latest tip of master Khem Raj
2016-07-07 18:08 ` [PATCH 3/4] musl: Update to v1.1.15 release Khem Raj
2016-07-07 18:08 ` [PATCH 4/4] bunutils: Upgrade to 2.26.1 Khem Raj
2016-07-08 13:50 ` [PATCH 0/4] musl/glibc/binutils updates Alexander Kanavin
2016-07-08 14:07   ` Khem Raj
2016-07-08 14:19     ` Alexander Kanavin
2016-07-13 10:14       ` André Draszik [this message]
2016-07-13 17:55         ` Khem Raj
2016-07-08 15:01   ` Burton, Ross

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=1468404872.23527.7.camel@andred.net \
    --to=git@andred.net \
    --cc=openembedded-core@lists.openembedded.org \
    /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.