From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFT][PATCH 0/2] Systemd 209
Date: Wed, 26 Feb 2014 11:00:40 +0200 [thread overview]
Message-ID: <530DAD38.7010506@linux.intel.com> (raw)
In-Reply-To: <6631D5B8-751A-458C-B9B2-7ACFDE88B065@gmail.com>
On 02/26/2014 09:14 AM, Khem Raj wrote:
>>>
>>> I did run test builds of the git version on the autobuilders and didn't
>>> see any failures?
>>
>>
>> builds might work but they won’t run and yes so far IFUNC support is needed so it won’t work on non-x86
>> architectures. One common runtime problem I am seeing is logind not being able to talk to dbus
>> across all architectures. I have pushed my latest rework to pull branch
>
> I have now refreshed my contrib tree
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/systemd-210
>
> I have documented additional change you might need in your distro if you are not
> using OE-Core’s fs-perms.txt, systemd now needs /var/run to be symlinked to /run
> or else it won’t be able to talk to d-bus and kdbus is too new to enable yet.
>
> Please try this patch, it now builds and boots fine on x86 and arm here. I am also
> testing out other architecture in meantime
>
Khem,
Did you test with ptest enabled in DISTRO_FEATURES? I just built it
locally and got the following error:
> | cp: cannot stat '/home/sgw/yocto/builds/world/tmp/work/core2-64-poky-linux/systemd/1_210-r0/build/rules': No such file or directory
> | WARNING: /home/sgw/yocto/builds/world/tmp/work/core2-64-poky-linux/systemd/1_210-r0/temp/run.do_install_ptest_base.9533:1 exit 1 from
> | cp -rf /home/sgw/yocto/builds/world/tmp/work/core2-64-poky-linux/systemd/1_210-r0/build/rules /home/sgw/yocto/builds/world/tmp/work/core2-64-poky-linux/systemd/1_210-r0/image/usr/lib/systemd/ptest/
> | ERROR: Function failed: do_install_ptest_base (log file is located at /home/sgw/yocto/builds/world/tmp/work/core2-64-poky-linux/systemd/1_210-r0/temp/log.do_install_ptest_base.9533)
Sau!
> -Khem
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2014-02-26 9:00 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 [this message]
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=530DAD38.7010506@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox