From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] perl: build with perlcross instead of qemu
Date: Fri, 9 Nov 2012 10:18:10 +0100 [thread overview]
Message-ID: <20121109101810.6f61c6a9@skate> (raw)
In-Reply-To: <509CC99A.4010700@mind.be>
On Fri, 09 Nov 2012 10:15:06 +0100, Arnout Vandecappelle wrote:
> Doesn't make sense. perlcross has to be extracted over the perl source: it
> replaces a few configuration scripts and creates a few more. There is nothing
> in there to install on the host or on the target.
First of all, thanks a lot for doing this work.
Do you have details on how perl-cross is maintained with regard to
perl? I.e, is it kept reasonably updated with new perl versions, or is
it a hack that works on a single perl version that will force us to
stay with only this version of perl?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-09 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 1:47 [Buildroot] [PATCH] perl: build with perlcross instead of qemu Arnout Vandecappelle
2012-11-09 3:01 ` Dan Pattison
2012-11-09 9:27 ` Arnout Vandecappelle
2012-11-09 7:19 ` Peter Korsgaard
2012-11-09 8:58 ` Alexander Khryukin
2012-11-09 9:15 ` Arnout Vandecappelle
2012-11-09 9:18 ` Thomas Petazzoni [this message]
2012-11-09 9:22 ` Arnout Vandecappelle
2012-11-09 9:15 ` Peter Korsgaard
2012-11-09 9:20 ` Arnout Vandecappelle
2012-11-09 9:23 ` Peter Korsgaard
2012-11-09 9:25 ` Peter Korsgaard
2012-11-09 10:31 ` Thomas Petazzoni
2012-11-09 10:36 ` Arnout Vandecappelle
2012-11-09 18:07 ` Arnout Vandecappelle
2012-11-09 21:13 ` François Perrad
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=20121109101810.6f61c6a9@skate \
--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