From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
poky@yoctoproject.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [PATCH 0/1] gnu-config make sure we use perl-native
Date: Mon, 14 Mar 2011 12:55:04 +0000 [thread overview]
Message-ID: <1300107304.30423.12.camel@rex> (raw)
In-Reply-To: <46D5E03C-9927-4F57-A6AC-7024B8478E1C@dominion.thruhere.net>
On Mon, 2011-03-14 at 13:18 +0100, Koen Kooi wrote:
> Op 14 mrt 2011, om 12:51 heeft Paul Eggleton het volgende geschreven:
>
> > On Saturday 12 March 2011 02:31:40 Khem Raj wrote:
> >>> Back to the drawing board on why the miss-match is occuring in
> >>> Config.pm then.
> >>
> >> somewhere there is /usr/bin/perl referred may be a cross recipe ?
> >
> > I've hit this issue this morning, and have filed a bug report:
> >
> > http://bugzilla.pokylinux.org/show_bug.cgi?id=866
> >
> > Not sure if it helps but at least it should be easy to reproduce.
>
> I haven't checked if the OE .dev and OE core gnu-config are similar, but have a look at:
>
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=be21179c5321bd0afb9221f020ac12ad75c86a3b
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=edcdefbf6e0675c1bcc1fc4f464f654223380e50
There are a few related patches to this floating around and I know Tom
did some work in OE.dev to make perl-native an early bootstrap
dependency.
I've been giving this some thought and given the various goals we have,
I think the long term best solution is going to be to place perl into an
isolated bin directory in sysroots, then for anything using really using
perl-native, add that directory to PATH. This is similar to what we now
do with the bootstrap toolchains in OE-Core. This way the dependencies
are deterministic and either perl is or isn't required but we don't
instantly need to build perl-native or run the risk of nasty loops in
the early bootstrap. Anything requiring perl-native would add the
directory to PATH, probably using a tiny class file.
The above patches still would make sense of course.
Cheers,
Richard
next prev parent reply other threads:[~2011-03-14 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 1:15 [PATCH 0/1] gnu-config make sure we use perl-native Saul Wold
2011-03-12 1:15 ` [PATCH 1/1] gnu-config: Ensure that we use perl-native to avoid version mis-matches Saul Wold
2011-03-12 1:34 ` [PATCH 0/1] gnu-config make sure we use perl-native Saul Wold
2011-03-12 2:31 ` [poky] " Khem Raj
2011-03-14 11:51 ` Paul Eggleton
2011-03-14 12:18 ` Koen Kooi
2011-03-14 12:55 ` Richard Purdie [this message]
2011-03-17 11:48 ` 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=1300107304.30423.12.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox