Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libnss-mdns: dont use hard coded /lib path
Date: Wed, 03 Aug 2011 16:17:00 +0100	[thread overview]
Message-ID: <1312384620.2344.681.camel@rex> (raw)
In-Reply-To: <1312384532-11310-1-git-send-email-galak@kernel.crashing.org>

On Wed, 2011-08-03 at 10:15 -0500, Kumar Gala wrote:
> As libdir might not be /lib (could be /lib64) use ${libdir} instead of
> hard coded "/lib" in configure options set in EXTRA_OECONF.

Do you mean ${libdir} or ${base_libdir} ?

> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
>  .../libnss-mdns/libnss-mdns_0.10.bb                |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-connectivity/libnss-mdns/libnss-mdns_0.10.bb b/meta/recipes-connectivity/libnss-mdns/libnss-mdns_0.10.bb
> index f5df005..00f2c56 100644
> --- a/meta/recipes-connectivity/libnss-mdns/libnss-mdns_0.10.bb
> +++ b/meta/recipes-connectivity/libnss-mdns/libnss-mdns_0.10.bb
> @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=2d5025d4aa3495befef8f17206a5b0a1"
>  
>  DEPENDS = "avahi"
>  RDEPENDS_${PN} = "avahi-daemon"
> -PR = "r2"
> +PR = "r3"
>  
>  SRC_URI = "http://0pointer.de/lennart/projects/nss-mdns/nss-mdns-${PV}.tar.gz"
>  
> @@ -21,7 +21,7 @@ inherit autotools
>  LEAD_SONAME = "libnss_mdns.so"
>  DEBIANNAME_${PN} = "libnss-mdns"
>  
> -EXTRA_OECONF = "--libdir=/lib --disable-lynx --enable-avahi"
> +EXTRA_OECONF = "--libdir=${libdir} --disable-lynx --enable-avahi"
>  
>  # TODO: pattern based configuration update
>  pkg_postinst_${PN} () {





  reply	other threads:[~2011-08-03 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 15:15 [PATCH] libnss-mdns: dont use hard coded /lib path Kumar Gala
2011-08-03 15:17 ` Richard Purdie [this message]
2011-08-03 15:20 ` Phil Blundell

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=1312384620.2344.681.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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