All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Nick D'Ademo <nickdademo@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: MULTILIB builds with Yocto: Status?
Date: Mon, 25 Nov 2013 10:17:02 +0000	[thread overview]
Message-ID: <1692310.DXcMCOQJZA@helios> (raw)
In-Reply-To: <CANR6C56G+sT0h3iXemO41Yf-knp4X9M96qv-CQK+oPN5VUtyPw@mail.gmail.com>

Hi Nick,

On Monday 25 November 2013 01:43:32 Nick D'Ademo wrote:
> Found the fix for these issues:
> 
> *The two offending Poky recipes are:*
> recipes-multimedia/x264
> recipes-multimedia/libav
> 
> *Files which need to be modified:*
> x264_git.bb -> Add --libdir=${libdir} to EXTRA_OECONF variable
> libav.inc -> Add --libdir=${libdir} AND --shlibdir=${libdir} to
> EXTRA_OECONF variable
> 
> As you can see from the above fixes, the issue was that the configure step
> was passing "usr/lib" instead of "usr/lib64" which ultimately caused the
> "installed but not shipped" errors.
> 
> Are these actually bugs which should be patched in the recipes?

These two recipes have their own custom (non-autotools) configure scripts and 
thus we compose our own configure command line to match; so yes we should fix 
these. Would you be able to send a patch on top of OE-Core to add the options 
to each recipe? There's a guide here if you need it:

http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-11-25 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 14:17 MULTILIB builds with Yocto: Status? Nick D'Ademo
2013-11-24  9:53 ` Nick D'Ademo
2013-11-24 14:43   ` Nick D'Ademo
2013-11-25 10:17     ` Paul Eggleton [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=1692310.DXcMCOQJZA@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=nickdademo@gmail.com \
    --cc=yocto@yoctoproject.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 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.