From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] perl: use archlib_exp config.sh variable
Date: Wed, 10 Oct 2012 11:00:50 +0800 [thread overview]
Message-ID: <5074E4E2.2090908@windriver.com> (raw)
In-Reply-To: <2bc985f69847a615429a908aa0e8f972a8be91f9.1349829329.git.tom.zanussi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2552 bytes --]
On 2012?10?10? 08:48, tom.zanussi@intel.com wrote:
> From: Tom Zanussi<tom.zanussi@intel.com>
>
> This patch uses an unmodified version of archlibexp called
> archlib_exp, introduced by a previous patch to config.sh, which is
> used to generate the correct value of ARCHLIB_EXP into config.h
>
> Fixes [YOCTO #3099].
>
> Signed-off-by: Tom Zanussi<tom.zanussi@intel.com>
> ---
> .../perl/perl-5.14.2/perl-archlib-exp.patch | 15 +++++++++++++++
> meta/recipes-devtools/perl/perl_5.14.2.bb | 3 ++-
> 2 files changed, 17 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-devtools/perl/perl-5.14.2/perl-archlib-exp.patch
>
> diff --git a/meta/recipes-devtools/perl/perl-5.14.2/perl-archlib-exp.patch b/meta/recipes-devtools/perl/perl-5.14.2/perl-archlib-exp.patch
> new file mode 100644
> index 0000000..1c170ef
> --- /dev/null
> +++ b/meta/recipes-devtools/perl/perl-5.14.2/perl-archlib-exp.patch
> @@ -0,0 +1,15 @@
> +Upstream-Status:Inappropriate [embedded specific]
> +
> +Index: perl-5.14.2/config_h.SH
> +===================================================================
> +--- perl-5.14.2.orig/config_h.SH
> ++++ perl-5.14.2/config_h.SH
> +@@ -996,7 +996,7 @@ sed<<!GROK!THIS!>$CONFIG_H -e 's!^#und
> + * in programs that are not prepared to deal with ~ expansion at run-time.
> + */
> + #$d_archlib ARCHLIB "$archlib" /**/
> +-#$d_archlib ARCHLIB_EXP "$archlibexp" /**/
> ++#$d_archlib ARCHLIB_EXP "$archlib_exp" /**/
> +
> + /* ARCHNAME:
> + * This symbol holds a string representing the architecture name.
> diff --git a/meta/recipes-devtools/perl/perl_5.14.2.bb b/meta/recipes-devtools/perl/perl_5.14.2.bb
> index 09b2acb..d9206d8 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 = "r10"
> +PR = "r11"
>
> # 5.10.1 has Module::Build built-in
> PROVIDES += "libmodule-build-perl"
> @@ -66,6 +66,7 @@ SRC_URI = "http://www.cpan.org/src/5.0/perl-${PV}.tar.gz \
> file://cross-generate_uudmap.patch \
> file://fix_bad_rpath.patch \
> file://perl-build-in-t-dir.patch \
> + file://perl-archlib-exp.patch \
> \
> file://config.sh \
> file://config.sh-32 \
test them for qemux86 and qemuppc, the @INC path is right now.
Regards,
Kai
[-- Attachment #2: Type: text/html, Size: 3757 bytes --]
next prev parent reply other threads:[~2012-10-10 3:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 0:48 [PATCH 0/2] perl: fix @INC, v2 tom.zanussi
2012-10-10 0:48 ` [PATCH 1/2] perl: add archlib_exp variable used to generate ARCHLIB_EXP in config.h tom.zanussi
2012-10-10 0:48 ` [PATCH 2/2] perl: use archlib_exp config.sh variable tom.zanussi
2012-10-10 3:00 ` Kang Kai [this message]
2012-10-10 3:24 ` Tom Zanussi
2012-10-10 14:14 ` [PATCH 0/2] perl: fix @INC, v2 Richard Purdie
2012-10-10 14:27 ` Tom Zanussi
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=5074E4E2.2090908@windriver.com \
--to=kai.kang@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