diff mbox

perl-cross: bump to version 0.9.7

Message ID 1435561397-27221-1-git-send-email-francois.perrad@gadz.org
State Accepted
Headers show

Commit Message

Francois Perrad June 29, 2015, 7:03 a.m. UTC
fix some build failures,
see https://github.com/arsv/perl-cross/issues/17

Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
---
 package/perl/perl.hash | 2 +-
 package/perl/perl.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Comments

Thomas Petazzoni June 29, 2015, 8:01 p.m. UTC | #1
Dear Francois Perrad,

On Mon, 29 Jun 2015 09:03:17 +0200, Francois Perrad wrote:
> fix some build failures,
> see https://github.com/arsv/perl-cross/issues/17
> 
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
>  package/perl/perl.hash | 2 +-
>  package/perl/perl.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied, thanks.

However, speaking of perl-cross, there is something that annoys me a
bit: the fact that we are patching the target variant of perl by
applying perl-cross, but not the host variant. I am currently working
on using per-package out of tree build. This means having a single
source tree for both the host and target variant of a given package: it
would no longer be allowed to patch the target variant in a given way,
and the host variant in another way.

Do you think it is possible to patch both the host and target perl in
the same way, and only depending on the configure options (or make
variables, or whatever), do the right thing?

Thanks!

Thomas
Francois Perrad June 30, 2015, 9:57 a.m. UTC | #2
2015-06-29 22:01 GMT+02:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
> Dear Francois Perrad,
>
> On Mon, 29 Jun 2015 09:03:17 +0200, Francois Perrad wrote:
>> fix some build failures,
>> see https://github.com/arsv/perl-cross/issues/17
>>
>> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
>> ---
>>  package/perl/perl.hash | 2 +-
>>  package/perl/perl.mk   | 2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> Applied, thanks.
>
> However, speaking of perl-cross, there is something that annoys me a
> bit: the fact that we are patching the target variant of perl by
> applying perl-cross, but not the host variant. I am currently working
> on using per-package out of tree build. This means having a single
> source tree for both the host and target variant of a given package: it
> would no longer be allowed to patch the target variant in a given way,
> and the host variant in another way.
>
> Do you think it is possible to patch both the host and target perl in
> the same way, and only depending on the configure options (or make
> variables, or whatever), do the right thing?
>

Dear Thomas,

perl-cross is not a serie of patches which fixes a broken configure script.
perl-cross is an add-on which adds an alternate configure script for
cross-compilation.
Currently, perl-cross is not extracted in the host-perl build tree,
because it is useless.
But if perl-cross is extracted, the original configure script works
fine for building a host-perl.

Alex Suykov could correct me or give more details.

Another point for perl, could you take to look to
http://patchwork.ozlabs.org/patch/477361/ ?

François.

> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot@busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Thomas Petazzoni July 1, 2015, 9:54 a.m. UTC | #3
Hello,

On Tue, 30 Jun 2015 11:57:05 +0200, François Perrad wrote:

> perl-cross is not a serie of patches which fixes a broken configure script.
> perl-cross is an add-on which adds an alternate configure script for
> cross-compilation.
> Currently, perl-cross is not extracted in the host-perl build tree,
> because it is useless.
> But if perl-cross is extracted, the original configure script works
> fine for building a host-perl.

Ok, good.

> Another point for perl, could you take to look to
> http://patchwork.ozlabs.org/patch/477361/ ?

Applied, thanks for the reminder.

Thomas
diff mbox

Patch

diff --git a/package/perl/perl.hash b/package/perl/perl.hash
index d28b5fd..0ee587e 100644
--- a/package/perl/perl.hash
+++ b/package/perl/perl.hash
@@ -4,4 +4,4 @@  sha1   63126c683b4c79c35008a47d56f7beae876c569f                         perl-5.2
 sha256 e5a4713bc65e1da98ebd833dce425c000768bfe84d17ec5183ec5ca249db71ab perl-5.20.2.tar.bz2
 
 # No upstream hashes for the following
-sha256 e25c5d9289b98db8f9d6a27bda9de12028ffc37eeede2d2fbfb10590d36fbf8f perl-5.20.2-cross-0.9.6.tar.gz
+sha256 36cabbc937cc66e59c8ae414d7753190d54a022cae0012c09ee5bbee78bc0aa0 perl-5.20.2-cross-0.9.7.tar.gz
diff --git a/package/perl/perl.mk b/package/perl/perl.mk
index 6f3cd49..591fa2e 100644
--- a/package/perl/perl.mk
+++ b/package/perl/perl.mk
@@ -12,7 +12,7 @@  PERL_LICENSE = Artistic or GPLv1+
 PERL_LICENSE_FILES = Artistic Copying README
 PERL_INSTALL_STAGING = YES
 
-PERL_CROSS_VERSION = 0.9.6
+PERL_CROSS_VERSION = 0.9.7
 PERL_CROSS_BASE_VERSION = 5.$(PERL_VERSION_MAJOR).2
 # DO NOT refactor with the github helper (the result is not the same)
 PERL_CROSS_SITE = http://raw.github.com/arsv/perl-cross/releases