From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] perl-gdgraph: new package
Date: Tue, 29 Jul 2014 18:29:29 -0300 [thread overview]
Message-ID: <53D81239.2070001@zacarias.com.ar> (raw)
In-Reply-To: <20140719223515.GL3593@free.fr>
On 07/19/2014 07:35 PM, Yann E. MORIN wrote:
Hi All.
Reviving this...
> Does that mean we should have our own host-perl, then?
>
> It would guarantee that we have a known situation, where we control the
> version of perl and we can reproduce builds across machines with
> different versions of perl and a known list of installed modules and
> their versions.
>
> It would also allow tweaking the search paths to no longer include the
> host system includes and libraries search paths (although it won't
> protect us from badly written packages, such as perl-net-ssleay.)
>
> But we can ensure that dependencies on other perl modules won't
> accidentally find host system perl's modules.
>
> This might be a big endeavour, but even if we only build our own
> host-perl, that's still a big improvement, and needs only little changes
> to our current perl infra, i.e. just calling our own perl.
>
> We can later enhance the situation by gradually tweaking our host-perl.
>
> What do you guys think of this?
Well according to my failur(es) on gentoo:
>>> perl-gd 2.53 Building
cd /home/gustavoz/b/perl/output/build/perl-gd-2.53/ && if [ -f Build.PL
] ; then perl Build build; else /usr/bin/make -j1
PERL_INC=/home/gustavoz/b/perl/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/perl5/5.18.2/arm-linux/CORE
pure_all; fi
make[1]: Entering directory
`/home/gustavoz/b/perl/output/build/perl-gd-2.53'
/usr/bin/perl5.18.2 GD/Image.pm.PLS GD/Image.pm
Extracting Image.pm (with variable substitutions)
cp GD/Image.pm blib/lib/GD/Image.pm
cp GD/Simple.pm blib/lib/GD/Simple.pm
cp GD.pm blib/lib/GD.pm
AutoSplitting blib/lib/GD.pm (blib/lib/auto/GD)
cp GD/Group.pm blib/lib/GD/Group.pm
cp GD/Polygon.pm blib/lib/GD/Polygon.pm
cp GD/Polyline.pm blib/lib/GD/Polyline.pm
cp qd.pl blib/lib/qd.pl
/usr/bin/perl5.18.2 /usr/lib64/perl5/5.18.2/ExtUtils/xsubpp -typemap
/usr/lib64/perl5/5.18.2/ExtUtils/typemap -typemap typemap GD.xs >
GD.xsc && mv GD.xsc GD.c
make[1]: *** No rule to make target
`/home/gustavoz/b/perl/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/perl5/5.18.2/arm-linux/CORE/patchlevel-gentoo.h',
needed by `GD.o'. Stop.
make[1]: Leaving directory `/home/gustavoz/b/perl/output/build/perl-gd-2.53'
make: *** [/home/gustavoz/b/perl/output/build/perl-gd-2.53/.stamp_built]
Error 2
Stumbled upon this when looking at the perl-gd xpm failure.
And surprise, it fails for a bunch of other perl packages as well.
We may be able to work around that, but really it would be a volatile
hack. I'm all for saving build time but fishing in the ocean with lake
kit... please no.
+1 for host-perl.
Regards.
next prev parent reply other threads:[~2014-07-29 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 13:43 [Buildroot] [PATCH 1/4] support/scripts/scancpan: automatically populates LICENSE_FILES Francois Perrad
2014-07-18 13:43 ` [Buildroot] [PATCH 2/4] perl-gd: new package Francois Perrad
2014-07-18 17:51 ` Thomas Petazzoni
2014-07-19 19:58 ` Yann E. MORIN
2014-07-19 23:16 ` Yann E. MORIN
2014-07-20 6:00 ` François Perrad
2014-07-20 14:10 ` Yann E. MORIN
2014-07-18 13:43 ` [Buildroot] [PATCH 3/4] perl-gdtextutil: " Francois Perrad
2014-07-18 13:43 ` [Buildroot] [PATCH 4/4] perl-gdgraph: " Francois Perrad
2014-07-19 17:10 ` Thomas Petazzoni
2014-07-19 20:28 ` François Perrad
2014-07-19 22:35 ` Yann E. MORIN
2014-07-19 22:44 ` Bernd Kuhls
2014-07-20 7:52 ` François Perrad
2014-07-29 21:29 ` Gustavo Zacarias [this message]
2014-07-30 18:27 ` [Buildroot] [UNSURE]Re: " François Perrad
2014-07-18 17:47 ` [Buildroot] [PATCH 1/4] support/scripts/scancpan: automatically populates LICENSE_FILES 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=53D81239.2070001@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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