Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] microperl: install host-microperl in $(HOST_DIR)/opt/perl
Date: Tue, 27 Mar 2012 09:12:53 +0200	[thread overview]
Message-ID: <20120327091253.777d527d@skate> (raw)
In-Reply-To: <cb1e211a5de6c88c39cd9890dbf823c0ff1766c3.1332831974.git.thomas.petazzoni@free-electrons.com>

Le Tue, 27 Mar 2012 09:06:18 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :

> This commit is a tentative at fixing some Perl-related build problems
> we are having nowadays, due to the fact that microperl now depends on
> host-microperl. Since the perl binary from host-microperl is installed
> in $(HOST_DIR)/usr/bin, it gets picked up when we run host tools like
> host-intltool, which were normally meant to be used against the
> distribution-provided Perl.
> 
> This problem currently causes between a third to half of the failures
> in our random build tests.
> 
> Another, cleaner, option would be to make host-intltool depend on
> host-microperl, but this would require every user needing intltool to
> build a host Perl interpreter, even if the real reason for build the
> host Perl interpreter is only needed for those who want to build the
> Perl interpreter for the target. This commit is really a test at
> trying another solution than adding this dependency, to see whether it
> turns out to be a reasonable trade-off or not. Later developments and
> improvements in the Perl area may require to switch to a different
> solution than the one implemented by this patch.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

I have tested
http://autobuild.buildroot.org/results/9980055bf8ebc1ea442f5affc3418eb869c4c90d/defconfig
without the patch, in which case we have the host-intltool problem.
With this patch, this problem disappears and this defconfig builds
until the end with no problem.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-03-27  7:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  7:06 [Buildroot] [pull request] Pull request for branch for-2012.05/perl Thomas Petazzoni
2012-03-27  7:06 ` [Buildroot] [PATCH 1/2] microperl: fix MICROPERL_INSTALL_TARGET_CMDS Thomas Petazzoni
2012-03-28  6:28   ` Peter Korsgaard
2012-03-27  7:06 ` [Buildroot] [PATCH 2/2] microperl: install host-microperl in $(HOST_DIR)/opt/perl Thomas Petazzoni
2012-03-27  7:12   ` Thomas Petazzoni [this message]
2012-03-28  6:54   ` Peter Korsgaard
2012-03-28  7:55     ` Thomas Petazzoni
2012-03-28  9:32       ` Peter Korsgaard
2012-03-28 10:40         ` Will Newton
2012-03-28 10:55           ` Thomas Petazzoni
2012-03-28 12:47             ` Will Newton
2012-03-28 12:52             ` Thomas Petazzoni
2012-03-28 13:01               ` Will Newton
2012-03-28 13:10                 ` Will Newton
2012-03-28 13:18                 ` Thomas Petazzoni
2012-03-28 14:00                   ` Will Newton
2012-03-28 15:46                     ` Thomas Petazzoni

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=20120327091253.777d527d@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