* [PATCH] systemd: set the location of the kill binary
@ 2013-02-26 17:35 Ross Burton
2013-02-26 17:41 ` Otavio Salvador
2013-02-26 18:06 ` Khem Raj
0 siblings, 2 replies; 5+ messages in thread
From: Ross Burton @ 2013-02-26 17:35 UTC (permalink / raw)
To: openembedded-core
Otherwise systemd uses AC_PROG_PATH and finds it in the sysroot, which won't
work on the target.
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
meta/recipes-core/systemd/systemd_197.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/systemd/systemd_197.bb b/meta/recipes-core/systemd/systemd_197.bb
index c765c18..44cd919 100644
--- a/meta/recipes-core/systemd/systemd_197.bb
+++ b/meta/recipes-core/systemd/systemd_197.bb
@@ -48,6 +48,8 @@ PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt"
# Compress the journal
PACKAGECONFIG[xz] = "--enable-xz,--disable-xz,xz"
+export ac_cv_path_KILL="/bin/kill"
+
# The gtk+ tools should get built as a separate recipe e.g. systemd-tools
EXTRA_OECONF = " --with-rootprefix=${base_prefix} \
--with-rootlibdir=${base_libdir} \
--
1.7.10.4
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] systemd: set the location of the kill binary
2013-02-26 17:35 [PATCH] systemd: set the location of the kill binary Ross Burton
@ 2013-02-26 17:41 ` Otavio Salvador
2013-02-26 17:42 ` Burton, Ross
2013-02-26 18:06 ` Khem Raj
1 sibling, 1 reply; 5+ messages in thread
From: Otavio Salvador @ 2013-02-26 17:41 UTC (permalink / raw)
To: Ross Burton; +Cc: Patches and discussions about the oe-core layer
On Tue, Feb 26, 2013 at 2:35 PM, Ross Burton <ross.burton@intel.com> wrote:
> Otherwise systemd uses AC_PROG_PATH and finds it in the sysroot, which won't
> work on the target.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/recipes-core/systemd/systemd_197.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-core/systemd/systemd_197.bb b/meta/recipes-core/systemd/systemd_197.bb
> index c765c18..44cd919 100644
> --- a/meta/recipes-core/systemd/systemd_197.bb
> +++ b/meta/recipes-core/systemd/systemd_197.bb
> @@ -48,6 +48,8 @@ PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt"
> # Compress the journal
> PACKAGECONFIG[xz] = "--enable-xz,--disable-xz,xz"
>
> +export ac_cv_path_KILL="/bin/kill"
This can be given in EXTRA_OECONF IIRC. Did you try it?
> # The gtk+ tools should get built as a separate recipe e.g. systemd-tools
> EXTRA_OECONF = " --with-rootprefix=${base_prefix} \
> --with-rootlibdir=${base_libdir} \
> --
> 1.7.10.4
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] systemd: set the location of the kill binary
2013-02-26 17:41 ` Otavio Salvador
@ 2013-02-26 17:42 ` Burton, Ross
2013-02-26 17:48 ` Otavio Salvador
0 siblings, 1 reply; 5+ messages in thread
From: Burton, Ross @ 2013-02-26 17:42 UTC (permalink / raw)
To: Otavio Salvador; +Cc: Patches and discussions about the oe-core layer
On 26 February 2013 17:41, Otavio Salvador <otavio@ossystems.com.br> wrote:
>> +export ac_cv_path_KILL="/bin/kill"
>
> This can be given in EXTRA_OECONF IIRC. Did you try it?
That would also work, yes. Is that the preferred style?
Ross
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] systemd: set the location of the kill binary
2013-02-26 17:42 ` Burton, Ross
@ 2013-02-26 17:48 ` Otavio Salvador
0 siblings, 0 replies; 5+ messages in thread
From: Otavio Salvador @ 2013-02-26 17:48 UTC (permalink / raw)
To: Burton, Ross; +Cc: Patches and discussions about the oe-core layer
On Tue, Feb 26, 2013 at 2:42 PM, Burton, Ross <ross.burton@intel.com> wrote:
> On 26 February 2013 17:41, Otavio Salvador <otavio@ossystems.com.br> wrote:
>>> +export ac_cv_path_KILL="/bin/kill"
>>
>> This can be given in EXTRA_OECONF IIRC. Did you try it?
>
> That would also work, yes. Is that the preferred style?
At least for me it makes more sense as it is being passed to change
configure behavior so makes sense to be there.
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] systemd: set the location of the kill binary
2013-02-26 17:35 [PATCH] systemd: set the location of the kill binary Ross Burton
2013-02-26 17:41 ` Otavio Salvador
@ 2013-02-26 18:06 ` Khem Raj
1 sibling, 0 replies; 5+ messages in thread
From: Khem Raj @ 2013-02-26 18:06 UTC (permalink / raw)
To: Ross Burton; +Cc: openembedded-core
On (26/02/13 17:35), Ross Burton wrote:
> Otherwise systemd uses AC_PROG_PATH and finds it in the sysroot, which won't
> work on the target.
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/recipes-core/systemd/systemd_197.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-core/systemd/systemd_197.bb b/meta/recipes-core/systemd/systemd_197.bb
> index c765c18..44cd919 100644
> --- a/meta/recipes-core/systemd/systemd_197.bb
> +++ b/meta/recipes-core/systemd/systemd_197.bb
> @@ -48,6 +48,8 @@ PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt"
> # Compress the journal
> PACKAGECONFIG[xz] = "--enable-xz,--disable-xz,xz"
>
> +export ac_cv_path_KILL="/bin/kill"
may be ac_cv_path_KILL="/usr/bin/env kill"
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-02-26 18:22 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-26 17:35 [PATCH] systemd: set the location of the kill binary Ross Burton
2013-02-26 17:41 ` Otavio Salvador
2013-02-26 17:42 ` Burton, Ross
2013-02-26 17:48 ` Otavio Salvador
2013-02-26 18:06 ` Khem Raj
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.