From: Colin Walters <walters@verbum.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [RFC 1/2] glib: upgrade to 2.32.4
Date: Tue, 17 Jul 2012 20:47:37 -0400 [thread overview]
Message-ID: <1342572457.2860.11.camel@lenny> (raw)
In-Reply-To: <5006049E.40509@linux.intel.com>
On Tue, 2012-07-17 at 17:34 -0700, Saul Wold wrote:
> It seems to be getting the native sysroot python instead of the more
> correct "#! /usr/bin/env python", this is causing a dependency failure.
>
> If you could look at this please.
I ran into this a while ago with flex/bison:
https://lists.yoctoproject.org/pipermail/poky/2012-January/007403.html
Apparently the "correct" fix is to set an environment variable like e.g.
PYTHON="/usr/bin/env python" ./configure --prefix=foo ?
That seems fairly gross though. Some more generic solution would be
nice...I don't have any great ideas offhand though. I wonder if there's
any actual use case for hardcoding the paths found at build time into
the generated binaries.
See also:
https://bugzilla.gnome.org/show_bug.cgi?id=650763
https://bugzilla.gnome.org/show_bug.cgi?id=670718
next prev parent reply other threads:[~2012-07-18 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 16:07 [RFC 1/2] glib: upgrade to 2.32.4 Martin Jansa
2012-07-16 16:07 ` [RFC 2/2] glib: package bash-completion files in separate package and move ${PN}-codegen to .inc Martin Jansa
2012-07-18 0:34 ` [RFC 1/2] glib: upgrade to 2.32.4 Saul Wold
2012-07-18 0:47 ` Colin Walters [this message]
2012-07-18 18:13 ` Richard Purdie
2012-07-18 18:18 ` Colin Walters
2012-07-18 21:20 ` Richard Purdie
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=1342572457.2860.11.camel@lenny \
--to=walters@verbum.org \
--cc=martin.jansa@gmail.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