From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] perl: Remove the changes of bin, lib etc. as the defaults will give sane values.
Date: Thu, 6 Sep 2012 14:43:53 -0500 [thread overview]
Message-ID: <5048FCF9.9070707@windriver.com> (raw)
In-Reply-To: <5048F57F.10002@linux.intel.com>
On 9/6/12 2:11 PM, Saul Wold wrote:
> On 09/06/2012 01:29 AM, Martin Ertsaas wrote:
>> The old config put stuff in ${perldir}/image/usr/local/oecore-x86_64/sysroot/x86_64-unknownsdk-linux/usr/local/oecore-x86_64/sysroots/x86_64-unknownsdk-linux/usr
>> instead of in ${perldir}/image/usr/local/oecore-x86_64/sysroot/x86_64-nimbussdk-linux/usr as it should.
>
> I am not sure we want to remove that sed code, since allows for
> different ${libdir} than /usr/lib, such as a flattened /lib, same with
> the ${exec_prefix}.
Ya, the sed lines are specifically there to enable the end user to modify the
exec_prefix and libdir to their local distribution policies. If this is no
longer necessary, we can remove it.. but someone needs to verify they are being
used properly. (Flattened filesystem and multilibs are the two places I know
it's used today.)
--Mark
> Sau!
>
>
>> ---
>> meta/recipes-devtools/perl/perl_5.14.2.bb | 19 ++++++++-----------
>> 1 files changed, 8 insertions(+), 11 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/perl/perl_5.14.2.bb b/meta/recipes-devtools/perl/perl_5.14.2.bb
>> index 3c1360f..04e2597 100644
>> --- a/meta/recipes-devtools/perl/perl_5.14.2.bb
>> +++ b/meta/recipes-devtools/perl/perl_5.14.2.bb
>> @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://Copying;md5=2b4c6ffbcfcbdee469f02565f253d81a \
>> # We need gnugrep (for -I)
>> DEPENDS = "virtual/db grep-native"
>> DEPENDS += "gdbm zlib"
>> -PR = "r9"
>> +PR = "r10"
>>
>> # 5.10.1 has Module::Build built-in
>> PROVIDES += "libmodule-build-perl"
>> @@ -145,16 +145,13 @@ do_configure() {
>>
>> ${@base_contains('DISTRO_FEATURES', 'largefile', '', 'do_nolargefile', d)}
>>
>> - # Update some paths in the configuration
>> - sed -i -e 's,@DESTDIR@,${prefix},g' \
>> - -e 's,@ARCH@-thread-multi,,g' \
>> - -e 's,@ARCH@,${TARGET_ARCH}-${TARGET_OS},g' \
>> - -e 's,@STAGINGDIR@,${STAGING_DIR_HOST},g' \
>> - -e "s%\([ \"^\',=]\+\)/usr/include%\1${STAGING_INCDIR}%g" \
>> - -e "s%\([ \"^\',=]\+\)/usr/lib/%\1${libdir}/%g" \
>> - -e "s%\([ \"^\',=]\+\)/usr/%\1${exec_prefix}/%g" \
>> - -e "s%/perl5%/perl%g" \
>> - config.sh-${TARGET_ARCH}-${TARGET_OS}
>> + # Update some paths in the configuration
>> + sed -i -e 's,@DESTDIR@,${prefix},g' \
>> + -e 's,@ARCH@-thread-multi,,g' \
>> + -e 's,@ARCH@,${TARGET_ARCH}-${TARGET_OS},g' \
>> + -e 's,@STAGINGDIR@,${STAGING_DIR_HOST},g' \
>> + -e "s%/perl5%/perl%g" \
>> + config.sh-${TARGET_ARCH}-${TARGET_OS}
>>
>> case "${TARGET_ARCH}" in
>> x86_64 | powerpc | s390)
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-09-06 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 8:29 [PATCH] perl: Remove the changes of bin, lib etc. as the defaults will give sane values Martin Ertsaas
2012-09-06 19:11 ` Saul Wold
2012-09-06 19:43 ` Mark Hatle [this message]
2012-09-10 5:51 ` Martin Ertsås
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=5048FCF9.9070707@windriver.com \
--to=mark.hatle@windriver.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