From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/2] ode: Explicitly disable double-precision with PACKAGECONFIG
Date: Thu, 27 Feb 2014 10:58:44 +0100 [thread overview]
Message-ID: <20140227095844.GZ26981@jama> (raw)
In-Reply-To: <1393456501-30516-1-git-send-email-Martin.Jansa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
On Thu, Feb 27, 2014 at 12:15:00AM +0100, Martin Jansa wrote:
> * when it's left for autodetection, configure fails for qemux86* when
> == and configure calls AC_TRY_RUN
Missing "$build_os" == "$target_os" added in master-next branch.
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta-oe/recipes-support/ode/ode_0.9.bb | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta-oe/recipes-support/ode/ode_0.9.bb b/meta-oe/recipes-support/ode/ode_0.9.bb
> index 1f3a5ca..8b9955e 100644
> --- a/meta-oe/recipes-support/ode/ode_0.9.bb
> +++ b/meta-oe/recipes-support/ode/ode_0.9.bb
> @@ -22,3 +22,7 @@ do_configure_append() {
>
> FILES_${PN} = "${libdir}/lib*${SOLIBS}"
>
> +PACKAGECONFIG ?= ""
> +# if it isn't explicitly selected and "$build_os" == "$target_os", then configure will run
> +# series of AC_TRY_RUN which won't work for cross-compilation and configure fails
> +PACKAGECONFIG[double-precision] = "--enable-double-precision,--disable-double-precision"
> --
> 1.9.0
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-02-27 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 23:15 [meta-oe][PATCH 1/2] ode: Explicitly disable double-precision with PACKAGECONFIG Martin Jansa
2014-02-26 23:15 ` [meta-oe][PATCH 2/2] ode: upgrade to 0.13 Martin Jansa
2014-02-27 0:07 ` Khem Raj
2014-02-27 9:48 ` Martin Jansa
2014-02-27 16:27 ` Khem Raj
2014-02-27 9:53 ` Martin Jansa
2014-02-27 9:58 ` Martin Jansa [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=20140227095844.GZ26981@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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