From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/5] Relocatable perl-native and use it always
Date: Sat, 29 Jan 2011 08:52:59 -0700 [thread overview]
Message-ID: <4D4437DB.40704@mentor.com> (raw)
In-Reply-To: <4D44296D.6040209@mentor.com>
On 01/29/2011 07:51 AM, Tom Rini wrote:
> On 01/29/2011 04:29 AM, Martin Jansa wrote:
>> On Fri, Jan 28, 2011 at 11:52:28AM -0700, Tom Rini wrote:
>>> Hey all,
>>>
>>> As I've talked about before[1] there's build reproducibility issues
>>> depending on when perl-native is built. After talking with Mark Hatle
>>> a little bit I started thinking about relocation in perl again and it
>>> turns out that starting in 5.10, upstream perl supports relocation.
>>>
>>> This in turn makes it less painful to make perl-native be what we use
>>> when we want perl runtime, nearly everywhere (since you can use pstaging
>>> to avoid it the time next time).
>>>
>>> This patch set drops perl 5.8.8 and bumps all of the perl stuffs PR,
>>> switches to relocatable perl-native, and then the big switch to using it
>>> early.
>>
>> Looks good and as we're using 5.10 already then for whole series:
>>
>> Acked-by: Martin Jansa<Martin.Jansa@gmail.com>
>
> Thanks.
>
>> Can we also get rid of legacy staging from recipes/perl/perl_5.10.1.bb ?
>
> Huh? I killed legacy staging in both perls a long time ago (and then
> Koen fixed up my thinkos).
OK, after some quick IRC, -ENOCOFFEE. It looks like it wouldn't be too
hard to kill legacy staging based on poky (we just need to install on
the target Config_heavy-${TARGET_SYS}.pl. I'll tackle that separately.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-01-29 15:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 18:52 [PATCH 0/5] Relocatable perl-native and use it always Tom Rini
2011-01-28 18:52 ` [PATCH 1/5] perl: Drop 5.8.8, bump PR in all perl recipes Tom Rini
2011-01-28 21:03 ` Frans Meulenbroeks
2011-01-28 18:52 ` [PATCH 2/5] perl-native: Switch to userelocatableinc and not shared libperl Tom Rini
2011-01-31 10:44 ` Enrico Scholz
2011-01-31 14:30 ` Tom Rini
2011-01-28 18:52 ` [PATCH 3/5] automake: Add perl-native as a dep rather than perl-runtime-native Tom Rini
2011-01-28 21:06 ` Frans Meulenbroeks
2011-01-28 18:52 ` [PATCH 4/5] autoconf: Add perl-native as a dep Tom Rini
2011-01-28 21:06 ` Frans Meulenbroeks
2011-01-28 18:52 ` [PATCH 5/5] bitbake.conf: Drop unused perl-native-runtime ASSUME_PROVIDED Tom Rini
2011-01-28 21:07 ` Frans Meulenbroeks
2011-01-28 20:14 ` [PATCH 0/5] Relocatable perl-native and use it always Koen Kooi
2011-01-28 21:32 ` Tom Rini
2011-01-29 8:16 ` Roman I Khimov
2011-01-29 14:52 ` Tom Rini
2011-01-29 11:29 ` Martin Jansa
2011-01-29 11:59 ` Frans Meulenbroeks
2011-01-29 14:52 ` Tom Rini
2011-01-29 14:51 ` Tom Rini
2011-01-29 15:52 ` Tom Rini [this message]
2011-01-29 16:45 ` Koen Kooi
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=4D4437DB.40704@mentor.com \
--to=tom_rini@mentor.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