Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: jackie.huang@windriver.com, Amy Fong <amy.fong@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] nativesdk-glib-2.0: cannot build on hosts without libffi.so.5
Date: Mon, 08 Jul 2013 08:29:12 -0700	[thread overview]
Message-ID: <51DADAC8.7020208@linux.intel.com> (raw)
In-Reply-To: <45395363a744785f10811752669eac4a7c43f52a.1373254421.git.jackie.huang@windriver.com>

On 07/07/2013 09:11 PM, jackie.huang@windriver.com wrote:
> From: Jackie Huang <jackie.huang@windriver.com>
>
> The compile phase of nativesdk-glib-2.0 tries to run some binaries built
> and since the -Wl,rpath doesn't specify the sysroot libraries with libffi.so.5,
> attempts to run the binrary on hosts without libffi.so.5 results in an error
> message complaining that it cannot find libffi.so.5, to fix this, specify
> -Wl,rpath == -Wl,rpath-link

I am not sure this makes sense, we have relocation code already, and 
glib-2.0 DEPENDS on libffi, so it should be available.  What binary is 
being run?  That same binary might be built for the target and would 
have to be run native, so I think this is not correct.

Sau!

>
> Signed-off-by: Amy Fong <amy.fong@windriver.com>
> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
> ---
>   meta/recipes-core/glib-2.0/glib-2.0_2.36.2.bb |    7 +++++++
>   1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.36.2.bb b/meta/recipes-core/glib-2.0/glib-2.0_2.36.2.bb
> index ffe34ac..bd4f526 100644
> --- a/meta/recipes-core/glib-2.0/glib-2.0_2.36.2.bb
> +++ b/meta/recipes-core/glib-2.0/glib-2.0_2.36.2.bb
> @@ -46,6 +46,13 @@ RDEPENDS_${PN}-ptest_append_libc-glibc = "\
>               eglibc-localedata-translit-cjk-variants \
>              "
>
> +BUILDSDK_LDFLAGS = "-L${STAGING_LIBDIR} \
> +                    -Wl,-rpath-link,${STAGING_LIBDIR} \
> +                    -Wl,-rpath,${STAGING_LIBDIR} -Wl,-O1 \
> +                    -L${STAGING_DIR_HOST}${base_libdir} \
> +                    -Wl,-rpath-link,${STAGING_DIR_HOST}${base_libdir} \
> +                    -Wl,-rpath,${STAGING_DIR_HOST}${base_libdir} -Wl,-O1"
> +
>   do_configure_prepend() {
>   	sed -i -e '1s,#!.*,#!${USRBINPATH}/env python,' ${S}/gio/gdbus-2.0/codegen/gdbus-codegen.in
>   }
>


      reply	other threads:[~2013-07-08 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  4:11 [PATCH 0/1] nativesdk-glib-2.0: cannot build on hosts without libffi.so.5 jackie.huang
2013-07-08  4:11 ` [PATCH 1/1] " jackie.huang
2013-07-08 15:29   ` 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=51DADAC8.7020208@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=amy.fong@windriver.com \
    --cc=jackie.huang@windriver.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