From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/7] systemd-211 upgrade and uclibc fixes
Date: Mon, 17 Mar 2014 11:31:16 +0000 [thread overview]
Message-ID: <1395055876.3808.38.camel@ted> (raw)
In-Reply-To: <cover.1394948105.git.raj.khem@gmail.com>
On Sat, 2014-03-15 at 22:42 -0700, Khem Raj wrote:
> Finally, managed to get systemd 211 to boot on uclibc and eglibc
> on all supported qemu machines, this should fix bug #5940
>
> Additional functionality in uclibc is needed to support this
> systemd
>
> gnutls, glib-2.0, intltool fixes are uclibc specific and are needed
> to get uclibc images going
>
> util-linux fix is moulded to support uclibc
>
> I have been testing this fix on the qemuarm/qemuppc/qemumips/qemux86/qemux86-64
> on both uclibc/eglibc images and its been working good.
>
> The following changes since commit 58aae40bbf8edd9c5ca70b2094eeb724391f1993:
>
> eglibc: Update SRC_URI to point to final download location (2014-03-13 20:44:48 -0700)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib kraj/systemd-211
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/systemd-211
>
> Khem Raj (7):
> uclibc: Implement clock_adjtime()
> uclibc: Remove iconv.h
> gnutls: Link in pthread explicitly for uclibc
> glib-2.0: Fix localedir expectations for uclibc
> util-linux: scanf_cv_alloc_modifier changed from 'as' -> 'ms'
> intltool: Define DATADIRNAME=share for uclibc based systems
> Upgrade to systemd 211+
I tried this on the autobuilder, with and without the pulseaudio 4->5
upgrade. The result was:
http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/111
http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/112
so I'm afraid I can't take the systemd part of this series. Its getting
late in the cycle for a pulseaudio 4->5 upgrade too :/
Does anyone have any strong opinions on this?
Cheers,
Richard
next prev parent reply other threads:[~2014-03-17 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 5:42 [PATCH 0/7] systemd-211 upgrade and uclibc fixes Khem Raj
2014-03-16 5:42 ` [PATCH 1/7] uclibc: Implement clock_adjtime() Khem Raj
2014-03-16 5:42 ` [PATCH 2/7] uclibc: Remove iconv.h Khem Raj
2014-03-16 5:42 ` [PATCH 3/7] gnutls: Link in pthread explicitly for uclibc Khem Raj
2014-03-16 5:42 ` [PATCH 4/7] glib-2.0: Fix localedir expectations " Khem Raj
2014-03-18 11:13 ` Burton, Ross
2014-03-18 14:19 ` Khem Raj
2014-03-16 5:42 ` [PATCH 5/7] util-linux: scanf_cv_alloc_modifier changed from 'as' -> 'ms' Khem Raj
2014-03-26 1:19 ` Robert Yang
2014-03-26 1:20 ` Khem Raj
2014-03-26 3:33 ` Robert Yang
2014-03-26 3:47 ` Khem Raj
2014-03-26 5:05 ` Robert Yang
2014-03-16 5:42 ` [PATCH 6/7] intltool: Define DATADIRNAME=share for uclibc based systems Khem Raj
2014-03-16 5:42 ` [PATCH 7/7] Upgrade to systemd 211+ Khem Raj
2014-03-17 11:31 ` Richard Purdie [this message]
2014-03-17 11:41 ` [PATCH 0/7] systemd-211 upgrade and uclibc fixes Martin Jansa
2014-03-17 12:29 ` Richard Purdie
2014-03-17 16:06 ` Khem Raj
2014-03-17 21:52 ` Richard Purdie
2014-03-17 22:05 ` Martin Jansa
2014-03-17 22:42 ` 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=1395055876.3808.38.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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