From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB
Date: Mon, 19 Mar 2012 16:57:31 +0100 [thread overview]
Message-ID: <20120319165731.4d3374cd@skate> (raw)
In-Reply-To: <d393625cf8a0f0af32c086413b19b091@zacarias.com.ar>
Le Mon, 19 Mar 2012 12:52:04 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> Reverted? It was never applied.
Sorry, my bad, I thought it had been applied and was the reason of the
failure. I will investigate what is causing this new breakage.
> We've already discussed this on IRC and i stand on my position about
> it.
> A cold host-microperl build takes roughly 2 minutes on my quite mundane
> desktop with it's slow hard drive.
> So please someone else(s) fix it as they see fit, i'm not submitting
> anything else perl-related.
> Future-proof doesn't seem to be the rule which is what i aimed at so
> i'll just quit doing anything perl-related which was mostly as a favour
> since i don't use it even though i code in perl for other purposes.
Gustavo, your work on Perl is really appreciated, but I think it's also
fair to have a discussion on the pros and cons of various changes.
I am completely in favor of a solution where host-microperl gets built
when microperl for the target is selected since as you say, it is the
only solution to reliably build XS Perl modules for the target.
However, I wanted us to *investigate* the potential solutions to build
host-microperl *only* when microperl for the target is selected, and
not when we need a simple random utility such as intltool running on
the host.
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-03-19 15:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 1:58 [Buildroot] microperl fixes and improvements Gustavo Zacarias
2012-03-12 1:58 ` [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB Gustavo Zacarias
2012-03-12 6:58 ` Thomas Petazzoni
2012-03-12 10:14 ` Gustavo Zacarias
2012-03-12 11:33 ` Thomas Petazzoni
2012-03-12 12:07 ` Gustavo Zacarias
2012-03-12 7:00 ` Thomas Petazzoni
2012-03-19 15:30 ` Thomas Petazzoni
2012-03-19 15:52 ` Gustavo Zacarias
2012-03-19 15:57 ` Thomas Petazzoni [this message]
2012-03-19 16:10 ` Gustavo Zacarias
2012-03-19 16:22 ` Peter Korsgaard
2012-03-19 16:38 ` Thomas Petazzoni
2012-03-12 1:58 ` [Buildroot] [PATCH 2/3] libxml-parser-perl: add missing dep and drop wrong paths Gustavo Zacarias
2012-03-12 7:01 ` Thomas Petazzoni
2012-03-12 9:49 ` Gustavo Zacarias
2012-03-12 7:46 ` Thomas Petazzoni
2012-03-12 10:07 ` Gustavo Zacarias
2012-03-12 11:31 ` Thomas Petazzoni
2012-03-12 11:46 ` Gustavo Zacarias
2012-03-12 1:58 ` [Buildroot] [PATCH 3/3] host-microperl: define module paths and other improvements Gustavo Zacarias
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=20120319165731.4d3374cd@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