From: ChenQi <Qi.Chen@windriver.com>
To: Jonathan Liu <net147@gmail.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] systemd: fix SULOGIN path
Date: Thu, 26 Mar 2015 10:10:06 +0800 [thread overview]
Message-ID: <55136A7E.70002@windriver.com> (raw)
In-Reply-To: <551254FE.7070709@gmail.com>
On 03/25/2015 02:26 PM, Jonathan Liu wrote:
> On 25/03/2015 5:03 PM, Chen Qi wrote:
>> Fix SULOGIN path so that rescue.service doesn't use `sulogin' from
>> the sysroot
>> part of the build on host, which would lead to errors like below when
>> booting
>> into rescue mode.
>>
>> /bin/sh:
>> /buildarea2/chenqi/poky/build-systemd/tmp/sysroots/x86_64-linux/sbin/sulogin:
>> not found
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> meta/recipes-core/systemd/systemd_219.bb | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta/recipes-core/systemd/systemd_219.bb
>> b/meta/recipes-core/systemd/systemd_219.bb
>> index f2d3c13..843e30b 100644
>> --- a/meta/recipes-core/systemd/systemd_219.bb
>> +++ b/meta/recipes-core/systemd/systemd_219.bb
>> @@ -123,6 +123,7 @@ do_configure_prepend() {
>> export AR="${HOST_PREFIX}gcc-ar"
>> export RANLIB="${HOST_PREFIX}gcc-ranlib"
>> export KMOD="${base_bindir}/kmod"
>> + export SULOGIN="${base_sbindir}/sulogin"
>> if [ -d ${S}/units.pre_sed ] ; then
>> cp -r ${S}/units.pre_sed ${S}/units
>> else
> Wasn't this already fixed by:
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-core/systemd/systemd_219.bb?id=8e19349b696d4a3e8576ba64e935cf3a43bc7940
> ?
>
> Regards,
> Jonathan
>
>
Yes, you are right.
I didn't notice it.
Please ignore this patch.
I've updated my repo to the latest one.
Thanks,
Chen Qi
prev parent reply other threads:[~2015-03-26 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 6:03 [PATCH 0/1] systemd: fix SULOGIN path Chen Qi
2015-03-25 6:03 ` [PATCH 1/1] " Chen Qi
2015-03-25 6:26 ` Jonathan Liu
2015-03-26 2:10 ` ChenQi [this message]
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=55136A7E.70002@windriver.com \
--to=qi.chen@windriver.com \
--cc=net147@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox