Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT][PATCH 0/2] Systemd 209
Date: Sat, 22 Feb 2014 13:03:40 +0100	[thread overview]
Message-ID: <20140222120340.GM3854@jama> (raw)
In-Reply-To: <CAMKF1srH-UE7rtqDZJGorWXwoQYdGwzTvZwK8mE5u0ooTikzjg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

On Fri, Feb 21, 2014 at 08:32:49AM -0800, Khem Raj wrote:
> On Fri, Feb 21, 2014 at 7:16 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > 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?
> 
> I think we dont have such a big legacy with systemd yet may be if its
> few packages then lets fix the packages instead of enabling legacy
> support if we can. in my local tree ( not yet pushed ) I was
> explicitly enabling it and disabling kdbus support to see if I can fix
> the logind not finding dbus issue
> it seems to happen for all architectures

Agreed,

I've found another one: polkit:

| checking for LIBSYSTEMD_LOGIN... no
| configure: error: libsystemd-login support requested but libsystemd-login library not found
| Configure failed. The contents of all config.log files follows to aid debugging
| /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/polkit/0.111-r0/polkit-0.111/config.log
| This file contains any messages produced by compilers while
| running configure, to aid debugging if configure makes a mistake.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-02-22 12:03 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
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 [this message]
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=20140222120340.GM3854@jama \
    --to=martin.jansa@gmail.com \
    --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