From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] pkg-perl: fix for Perl XS packages configured by a Makefile.PL
Date: Sun, 20 Apr 2014 17:38:31 +0200 [thread overview]
Message-ID: <20140420173831.49d0cb23@skate> (raw)
In-Reply-To: <1398006356-5425-1-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Sun, 20 Apr 2014 17:05:55 +0200, Francois Perrad wrote:
> for native package, ExtUtils::MakeMaker detects all include filenames on system perl,
> all these includes will be required by the generated Makefile but on STAGING_DIR.
>
> patchlevel-debian.h is not a part of the Perl distribution,
> but it was added by some Linux distributions (Debian, Ubuntu, ...)
> In this case, we create an empty file on STAGING_DIR.
I'm sorry, but unfortunately, I don't understand this explanation. How
the fact that a header file is added by Linux distributions affecting
Buildroot? What package needs that? Which problem is this fixing?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-20 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 15:05 [Buildroot] [PATCH 1/2] pkg-perl: fix for Perl XS packages configured by a Makefile.PL Francois Perrad
2014-04-20 15:05 ` [Buildroot] [PATCH 2/2] perl-cross: bump to version 0.8.5 Francois Perrad
2014-04-20 15:37 ` Thomas Petazzoni
2014-04-20 17:12 ` François Perrad
2014-04-20 18:44 ` Thomas Petazzoni
2014-04-20 15:38 ` Thomas Petazzoni [this message]
2014-04-22 6:01 ` [Buildroot] [PATCH 1/2] pkg-perl: fix for Perl XS packages configured by a Makefile.PL Arnout Vandecappelle
2014-04-22 16:58 ` 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=20140420173831.49d0cb23@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.