All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFT][PATCH 0/2] Systemd 209
Date: Sat, 22 Feb 2014 08:49:21 +0000	[thread overview]
Message-ID: <1393058961.5181.4.camel@ted> (raw)
In-Reply-To: <8730C02B-B94E-4873-88D1-E5BA9063B585@dominion.thruhere.net>

On Sat, 2014-02-22 at 08:57 +0100, Koen Kooi wrote:
> Op 21 feb. 2014, om 16:21 heeft Richard Purdie <richard.purdie@linuxfoundation.org> het volgende geschreven:
> 
> > On Fri, 2014-02-21 at 16:16 +0100, Martin Jansa wrote:
> >> On Thu, Feb 20, 2014 at 02:18:56AM -0800, Khem Raj wrote:
> >>> This patchset upgrades systemd to 209 as can be seen some enahancements
> >>> to uclibc were neeed. As of now. It builds for me on both uclibc/eglibc
> >>> Please test it out in your setups and report back any issues
> >>> 
> >>> The following changes since commit 9a98b8bfe13b94d89a9e39cca821f26fdeaeffc3:
> >>> 
> >>>  image_types.bbclass: Fix tar IMAGE_CMD to not change directories (2014-02-18 08:37:03 +0000)
> >>> 
> >>> are available in the git repository at:
> >>> 
> >>>  git://git.openembedded.org/openembedded-core-contrib kraj/systemd-209
> >>>  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/systemd-209
> >>> 
> >>> Khem Raj (2):
> >>>  uclibc: Add new functionality needed for systemd 209
> >>>  systemd: Upgrade 208 -> 209
> >> 
> >> Thanks for upgrade
> >> 
> >> I've noticed pulseaudio failing to build when it tries to detect old
> >> libsystemd-login lib:
> >> 
> >> | to the PKG_CONFIG_PATH environment variable
> >> | No package 'libsystemd-login' found
> >> | configure:26263: $? = 1
> >> | configure:26277: result: no
> >> | No package 'libsystemd-login' found
> >> | configure:26310: error: *** Needed systemd support not found
> >> 
> >> do we want to enable compat libs or update pulseaudio to use new
> >> libsystemd?
> > 
> > FWIW the git recipe I was using enabled compat-libs...
> 
> And that needs IFUNC which only x86 toolchains support :(

I did run test builds of the git version on the autobuilders and didn't
see any failures? 

Cheers,

Richard



  reply	other threads:[~2014-02-22  8:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 10:18 [RFT][PATCH 0/2] Systemd 209 Khem Raj
2014-02-21  3:48 ` Saul Wold
2014-02-21  3:50   ` Khem Raj
2014-02-21 15:16 ` Martin Jansa
2014-02-21 15:21   ` Richard Purdie
2014-02-21 16:33     ` Khem Raj
2014-02-22  7:57     ` Koen Kooi
2014-02-22  8:49       ` Richard Purdie [this message]
2014-02-22  9:31         ` Khem Raj
2014-02-22 18:12           ` Phil Blundell
2014-02-22 19:52             ` Khem Raj
2014-02-23  7:36               ` Koen Kooi
2014-02-25  0:28                 ` Martin Jansa
2014-02-22 20:47             ` Martin Jansa
2014-02-22 21:12               ` Khem Raj
2014-02-26  7:14           ` Khem Raj
2014-02-26  9:00             ` Saul Wold
2014-02-26 17:58               ` Khem Raj
2014-02-21 16:32   ` Khem Raj
2014-02-22 12:03     ` Martin Jansa
2014-02-22 17:29       ` [meta-oe][PATCH] polkit: make it compatible with systemd-209 Martin Jansa
2014-02-22 17:29         ` [PATCH] pulseaudio: Make " Martin Jansa
2014-02-22 18:10           ` 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=1393058961.5181.4.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen@dominion.thruhere.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.