Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 1/2] pkg-perl: fix for Perl XS packages configured by Makefile.PL
Date: Wed, 11 Jun 2014 11:18:14 +0200	[thread overview]
Message-ID: <87egyvkdnt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1398356762-12486-1-git-send-email-francois.perrad@gadz.org> (Francois Perrad's message of "Thu, 24 Apr 2014 18:26:01 +0200")

>>>>> "Francois" == Francois Perrad <fperrad@gmail.com> writes:

 > ExtUtils::MakeMaker adds all the header files used by the perl as
 > dependencies to the generated Makefile. This means that the generated
 > Makefile will depend on the system's header files.

 > Usually this is not a problem, because when building the target package,
 > these header files will indeed be found in $(STAGING_DIR). However, some
 > distro's add an extra header file to the system's perl. This header is
 > also included in the generated Makefile, which makes the build fail
 > because it doesn't exist in $(STAGING_DIR).

 > As a work-around, explicitly create this header file in $(STAGING_DIR).
 > It doesn't hurt to create it even if the system perl doesn't need it.

 > Signed-off-by: Francois Perrad <francois.perrad@gadz.org>

Committed, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2014-06-11  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 16:26 [Buildroot] [V2 1/2] pkg-perl: fix for Perl XS packages configured by Makefile.PL Francois Perrad
2014-04-24 16:26 ` [Buildroot] [V2 2/2] perl-cross: bump to version 0.8.5 Francois Perrad
2014-04-28 16:46   ` Arnout Vandecappelle
2014-06-11  9:18   ` Peter Korsgaard
2014-04-28 16:26 ` [Buildroot] [V2 1/2] pkg-perl: fix for Perl XS packages configured by Makefile.PL Arnout Vandecappelle
2014-06-11  9:18 ` Peter Korsgaard [this message]

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=87egyvkdnt.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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