From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: python automake dirs (was meta-toolchain-sdk failure)
Date: Wed, 10 Aug 2011 18:22:46 +0100 [thread overview]
Message-ID: <1312996966.14274.388.camel@rex> (raw)
In-Reply-To: <E0030AC3-67DD-4AC7-ADB1-B83C423F7ECF@kernel.crashing.org>
On Wed, 2011-08-10 at 11:51 -0500, Kumar Gala wrote:
> On Aug 10, 2011, at 9:44 AM, Khem Raj wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> >> So the root of this seems to stem from the following in automake's
> >> python.m4:
> >>
> >> am_cv_python_pythondir=$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages
> >>
> >>
> > am_cv_python_pyexecdir=$PYTHON_EXEC_PREFIX/lib/python$PYTHON_VERSION/site-packages
> >>
> >> So the question at hand is how to fix this?
> >>
> >> Do we patch automake to respect libdir setting for these?
> >>
> >
> > yes seems sane to me
>
> posted some patches in which I do this via python-dir.bbclass which I think is better
I think I'm in favour of changing the m4 files in this case now I better
understand the problem...
Cheers,
Richard
prev parent reply other threads:[~2011-08-10 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 13:45 meta-toolchain-sdk failure Kumar Gala
2011-08-09 13:58 ` Richard Purdie
2011-08-09 15:32 ` Kumar Gala
2011-08-09 16:50 ` python automake dirs (was meta-toolchain-sdk failure) Kumar Gala
2011-08-10 14:44 ` Khem Raj
2011-08-10 16:51 ` Kumar Gala
2011-08-10 17:22 ` Richard Purdie [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=1312996966.14274.388.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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