All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: Change systemd_unitdir definition
Date: Sat, 27 Oct 2012 18:14:17 -0700	[thread overview]
Message-ID: <508C86E9.5030907@linux.intel.com> (raw)
In-Reply-To: <1351235029-31096-1-git-send-email-raj.khem@gmail.com>

On 10/26/2012 12:03 AM, Khem Raj wrote:
> systemd_unitdir indicates the arch independent
> files which are basically scripts and unit files
> and systemd wants then to be in /lib always even
> when base_libdir is  /lib64, hence we have to reflect
> that and not use base_libdir to define it. Otherwise
> on architectures where base_libdir is lib64 e.g. ppc64
> or multilibbed x86_64 this wont work
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>   meta/conf/bitbake.conf |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 5cb5b13..e7fa731 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -31,6 +31,7 @@ export localstatedir = "${base_prefix}/var"
>   export infodir = "${datadir}/info"
>   export mandir = "${datadir}/man"
>   export docdir = "${datadir}/doc"
> +export systemd_unitdir = "/lib/systemd"
>
>   # Architecture dependent paths
>   export bindir = "${exec_prefix}/bin"
> @@ -39,7 +40,6 @@ export libexecdir = "${exec_prefix}/libexec"
>   export libdir = "${exec_prefix}/${baselib}"
>   export includedir = "${exec_prefix}/include"
>   export oldincludedir = "${exec_prefix}/include"
> -export systemd_unitdir = "${base_libdir}/systemd"
>   localedir = "${libdir}/locale"
>
>   # Linkage between native/cross/nativesdk layouts
>
Merged into OE-Core

Thanks
	Sau!




      reply	other threads:[~2012-10-28  1:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26  7:03 [PATCH] bitbake.conf: Change systemd_unitdir definition Khem Raj
2012-10-28  1:14 ` Saul Wold [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=508C86E9.5030907@linux.intel.com \
    --to=sgw@linux.intel.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 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.