Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mylene Josserand <mylene.josserand@free-electrons.com>,
	openembedded-core@lists.openembedded.org
Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
	"Antoine Ténart" <antoine.tenart@free-electrons.com>,
	"Alexey Brodkin" <Alexey.Brodkin@synopsys.com>
Subject: Re: ARC arch support: uClibc status ?
Date: Fri, 23 Jun 2017 14:40:21 +0100	[thread overview]
Message-ID: <1498225221.24449.128.camel@linuxfoundation.org> (raw)
In-Reply-To: <a63a60dd-1000-0bf3-8fc1-5517b88e222d@free-electrons.com>

Hi,

On Fri, 2017-06-23 at 15:23 +0200, Mylene Josserand wrote:
> We are currently adding to Yocto project the Synopsys ARC CPU
> architecture, which is only available with uClibc library.
> 
> We currently have a layer which adds the support of this
> architecture 
> and uClibc support as it is, now, removed from OE-core.
> 
> Many configurations/fixes are needed in OpenEmbedded-core's recipes
> to 
> build successfully with this C library (library's dependencies, 
> autotools configuration, etc).
> 
> We wanted to send patches to fix them but it seems that all uClibc's 
> references are now removed from OE-core, even in recipes:
> 
> https://patchwork.openembedded.org/patch/140943/
> https://patches.openembedded.org/patch/140906/
> 
> What is the status of it? Remove entirely uClibc from OE-core?
> Could you give us advice on how to handle uClibc?  Should we create
> a 
> "meta-uclibc" layer which adds support of it + bbappend for all the 
> OE-core's recipes that currently fail because of uClibc's
> misconfiguration?
> 
> I guess that there is no plan to add uClibc's configuration in OE-
> core's 
> recipes (even without uClibc itself), right?

We dropped uclibc from OE-Core around a year ago in favour of musl
since it seems to work for all the use cases we've been aware of from
our users and nobody was willing to maintain it.

Since then the uclibc overrides and other pieces in core have bitrotted
to the point it was clear nobody was actively using or maintaining
them. I therefore proposed some patches removing them, those were
agreed by several developers and no objections were seen. We therefore
cleaned up the remaining pieces.

I believe that we have enhanced the extension mechanisms within the
core such that a meta-uclibc layer would be possible now, even for the
site files and insane.bbclass mappings and so on. It would need to add
some of the extensions removed from the core and then it should be
buildable again.

If you can't make anything work from the layer let us know and we can
try and figure out a way to solve that. I don't think the uclibc pieces
would be coming back into OE-Core any time soon though as whilst it
does have some niche markets left (e.g. arc), I can't see it being
widely used by the majority of OE users/arches.

(As an aside I haven't looked at it at all but does musl support arc?)

Cheers,

Richard



  reply	other threads:[~2017-06-23 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 13:23 ARC arch support: uClibc status ? Mylene Josserand
2017-06-23 13:40 ` Richard Purdie [this message]
2017-06-23 13:46   ` Khem Raj
     [not found]     ` <1498225858.3451.20.camel@synopsys.com>
2017-06-23 13:54       ` 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=1498225221.24449.128.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=antoine.tenart@free-electrons.com \
    --cc=mylene.josserand@free-electrons.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=thomas.petazzoni@free-electrons.com \
    /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