Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: update uClibc-ng to latest version 1.0.11
Date: Wed, 13 Jan 2016 20:49:41 +0100	[thread overview]
Message-ID: <20160113194941.GY19876@waldemar-brodkorb.de> (raw)
In-Reply-To: <87d1t679l2.fsf@dell.be.48ers.dk>

Hi Peter,
Peter Korsgaard wrote,

> >>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:
> 
>  > Update to 1.0.11. Contains a lot of bugfixes
>  > and some new features:
>  >  * mips{32r6,64r6} enablement
>  >  * argp support
>  >  * support for very simple /etc/gai.conf
>  >  * Xtensa nommu vfork fix
>  >  * systemd portability fixes
> 
> Does this mean that systemd can be now used with uClibc-NG?

In theory yes. OpenEmbedded recently switched to uClibc-ng and
I got some bug reports regarding systemd. I debugged and tested
some issues with buildroot, but I am not very interested in systemd
myself. It needs some patching of systemd and some options disabled.

So if anybody cares, you could take a look at oe git.

But as with all new features and bugfixes for uClibc-ng, it will not
work for any external uClibc toolchain or any internal uClibc
0.9.33.2 users.

best regards
 Waldemar

  reply	other threads:[~2016-01-13 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 17:58 [Buildroot] [PATCH] uclibc: update uClibc-ng to latest version 1.0.11 Waldemar Brodkorb
2016-01-12 21:48 ` Peter Korsgaard
2016-01-13 19:49   ` Waldemar Brodkorb [this message]
2016-01-13 21:42     ` Peter Korsgaard

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=20160113194941.GY19876@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