From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package
Date: Sun, 27 Aug 2017 07:11:18 +0200 [thread overview]
Message-ID: <7F016C7D-1A3D-4B5E-9E0D-F575D0976265@openadk.org> (raw)
In-Reply-To: <CAFSsvmr9ZWp8yh+ve88RDUsBQS9PxgZRWTjAkotaECQ13wNeJg@mail.gmail.com>
Hi,
> I highly doubt that considering OE/Yocto uses uclibc as well as glibc.
> They even
> have a bunch of patches to get SystemD working with uclibc.
OE no longer supports uclibc/uclibc-ng.
Yocto just seems to carry an old recipe for uclibc.
Latest release of uClibc-ng and systemd no longer requires any patches, so this shows how old the uclibc-ng support in OE might be, if there are still leftovers.
best regards
Waldemar
next prev parent reply other threads:[~2017-08-27 5:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 0:54 [Buildroot] [RFC PATCH 0/2] add gobject-introspection Sam Bobroff
2017-02-23 0:54 ` [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package Sam Bobroff
2017-02-23 9:18 ` Thomas Petazzoni
2017-02-24 4:07 ` Sam Bobroff
2017-02-24 8:25 ` Thomas Petazzoni
2017-02-27 14:58 ` Arnout Vandecappelle
2017-02-27 15:06 ` Baruch Siach
2017-02-27 23:22 ` Sam Bobroff
2017-08-15 10:47 ` Adam Duskett
2017-08-17 6:44 ` Alexey Roslyakov
2017-08-17 22:39 ` Arnout Vandecappelle
2017-08-22 10:57 ` Adam Duskett
2017-08-24 23:03 ` Arnout Vandecappelle
2017-08-26 16:01 ` Adam Duskett
2017-08-27 5:11 ` Waldemar Brodkorb [this message]
2017-08-27 15:15 ` Adam Duskett
2017-02-27 15:58 ` Thomas Petazzoni
2017-02-27 22:54 ` Sam Bobroff
2017-02-23 13:02 ` Baruch Siach
2017-02-23 13:44 ` Jérôme Pouiller
2017-02-23 0:54 ` [Buildroot] [RFC PATCH 2/2] package/libvips: enable introspection Sam Bobroff
2017-02-23 9:19 ` Thomas Petazzoni
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=7F016C7D-1A3D-4B5E-9E0D-F575D0976265@openadk.org \
--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 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.