Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: install files in ${libdir}, not in ${base_libdir}
Date: Thu, 12 Jun 2014 23:46:02 +0800	[thread overview]
Message-ID: <5399CB3A.3020506@windriver.com> (raw)
In-Reply-To: <1402580166-30993-1-git-send-email-enrico.scholz@sigma-chemnitz.de>


On 06/12/2014 09:36 PM, Enrico Scholz wrote:
> ${base_libdir} is not in the search path of -native binaries and they
> will try to pick the wrong openssl libraries.

Hello, I don't quite understand this, why it doesn't search
${base_libdir}, please ?

// Robert

>
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> ---
>   meta/recipes-connectivity/openssl/openssl.inc | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl.inc b/meta/recipes-connectivity/openssl/openssl.inc
> index b839c00..f17f829 100644
> --- a/meta/recipes-connectivity/openssl/openssl.inc
> +++ b/meta/recipes-connectivity/openssl/openssl.inc
> @@ -32,6 +32,10 @@ export AS = "${CC} -c"
>
>   inherit pkgconfig siteinfo multilib_header ptest
>
> +# natives don't generally look in base_libdir
> +base_libdir_class-native = "${libdir}"
> +base_libdir_class-nativesdk = "${libdir}"
> +
>   PACKAGES =+ "libcrypto libssl ${PN}-misc openssl-conf"
>   FILES_libcrypto = "${base_libdir}/libcrypto${SOLIBS}"
>   FILES_libssl = "${libdir}/libssl.so.*"
>


  reply	other threads:[~2014-06-12 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 13:36 [PATCH] openssl: install files in ${libdir}, not in ${base_libdir} Enrico Scholz
2014-06-12 15:46 ` Robert Yang [this message]
2014-06-13 10:03   ` Enrico Scholz

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=5399CB3A.3020506@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --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