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] perl-cross: bump to version 0.9.7
Date: Mon, 29 Jun 2015 22:01:28 +0200	[thread overview]
Message-ID: <20150629220128.2cdc5b25@free-electrons.com> (raw)
In-Reply-To: <1435561397-27221-1-git-send-email-francois.perrad@gadz.org>

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-06-29 20:01 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 [this message]
2015-06-30  9:57   ` François Perrad
2015-07-01  9:54     ` 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=20150629220128.2cdc5b25@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