From: Christopher McCrory <chrismcc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/2] Hack for perl module subdirectories
Date: Mon, 13 Aug 2018 10:56:43 -0700 [thread overview]
Message-ID: <20180813175645.11088-1-chrismcc@gmail.com> (raw)
When perl modules have Makefiles in subdirectories, not all of the
arguments to Makefile.PL get propagated to subdirectory/Makefile.PL.
This causes compile failures. Two examples are template-toolkit and
xml-parser. A hack is to fix them after the usual configure step.
Something like this:
$(SED) "s:^AR = .*:AR = $(TARGET_AR):g" $(@D)/Expat/Makefile
for AR, CC, xFLAGS, etc. This "works", but there should be a better
way. Hence the RFC.
Also there is a package, libxml-parser-perl, that is a host only perl
xml-parser package needed by host-intltool and metacity. Should they
stay seprate or be merged?
Christopher McCrory (2):
perl-template-toolkit: new package
perl-xml-parser: new package
DEVELOPERS | 2 ++
package/Config.in | 2 ++
package/perl-template-toolkit/Config.in | 11 ++++++++
.../perl-template-toolkit.hash | 6 ++++
.../perl-template-toolkit/perl-template-toolkit.mk | 32 ++++++++++++++++++++++
5 files changed, 53 insertions(+)
create mode 100644 package/perl-template-toolkit/Config.in
create mode 100644 package/perl-template-toolkit/perl-template-toolkit.hash
create mode 100644 package/perl-template-toolkit/perl-template-toolkit.mk
--
2.14.4
next reply other threads:[~2018-08-13 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 17:56 Christopher McCrory [this message]
2018-08-13 17:56 ` [Buildroot] [RFC PATCH 1/2] perl-template-toolkit: new package Christopher McCrory
2018-08-14 4:21 ` François Perrad
2018-08-15 12:03 ` Christopher McCrory
2018-08-15 18:06 ` François Perrad
2018-08-15 20:24 ` Christopher McCrory
2018-08-13 17:56 ` [Buildroot] [RFC PATCH 2/2] perl-xml-parser: " Christopher McCrory
2018-08-13 21:05 ` Thomas Petazzoni
2018-08-13 21:54 ` Christopher McCrory
2018-08-13 21:03 ` [Buildroot] [RFC PATCH 0/2] Hack for perl module subdirectories 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=20180813175645.11088-1-chrismcc@gmail.com \
--to=chrismcc@gmail.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