From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] perl-cross: bump to version 0.9.7
Date: Wed, 1 Jul 2015 11:54:19 +0200 [thread overview]
Message-ID: <20150701115419.4734e37c@free-electrons.com> (raw)
In-Reply-To: <CAB0FRst5vQG3G2+6n5Hc3nyCF+vWdqvcFYtEmf29U9TVzHPcew@mail.gmail.com>
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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-01 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 7:03 [Buildroot] [PATCH] perl-cross: bump to version 0.9.7 Francois Perrad
2015-06-29 20:01 ` Thomas Petazzoni
2015-06-30 9:57 ` François Perrad
2015-07-01 9:54 ` Thomas Petazzoni [this message]
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=20150701115419.4734e37c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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