Re: Multiarching perl
+++ Niko Tyni [2012-09-21 22:13 +0300]:
> On Wed, Sep 12, 2012 at 07:12:05PM +0100, Wookey wrote:
> > Does this mean you have some kind of patch for this stuff? Even if
> > it's pretty raw, it should save me/riku some time on knocking up a
> > multiarch package to test with. And it would help me grok some of
> > what's been discussed.
> Yeah. Sorry for the delay, I have serious trouble finding the time for
> this stuff.
No probs, I know what it's like. Your efforts are much appreciated.
> I managed something of a sprint on it a month or so ago, then got stuck
> thinking about the wider implications on the perl part of the archive.
> I've pushed the current state on the 'ntyni/multiarch-5.14' branch of
> This is work in progress, no guarantees about not rewriting history yet.
OK. Do you expect that to build as it stands?
I tried a simple-minded dpkg-buildpackage in that branch and it got as
Making all in ext/DynaLoader
/usr/bin/make all PERL_CORE=1 LIBPERL_A=libperl.so.5.14.2 LINKTYPE=static
make: Entering directory /home/wookey/linaro/multiarch/packages/perlgit/ext/DynaLoader'
make: Leaving directory /home/wookey/linaro/multiarch/packages/perlgit/ext/DynaLoader'
cc -o perl -Wl,-z,relro -fstack-protector -L/usr/local/lib -Wl,-E
perlmain.o libperl.so.5.14.2 cat ext.libs -ldl -lm -lpthread -lc -lcrypt
Can't locate File/Spec.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5
/usr/share/perl/5.14 /usr/local/lib/site_perl .) at /usr/bin/gcc.real line 4.
BEGIN failed--compilation aborted at /usr/bin/gcc.real line 4.
Perhaps some other work is needed to debian-build perl from git? I didn't see anything in
README.source of README.Debian saying to do something special.
I do have Spec.pm in /usr/lib/perl/5.14.2/File/ (from perl-base). So should @INC include that dir
on the path? Not sure if this is a building MA version on pre-MA setup issue?
If you expect it to build OK then I'll look a bit harder at what's actually amiss.
> I've tried to grok the multiarch specs better, but I'm still not sure if
> perl-base needs to be M-A:allowed or M-A:foreign, and how the perlapi-*
> ABI version specification fits into this.
> In the wider view, do we need to (eventually) add M-A tags on all the perl
> module packages in the archive to make things like a foreign architecture
> irssi perl plugin generally usable? Can an arch:all perl module package
> be M-A:foreign? What if it depends on an arch:any perl module package?
> And so forth.
Hmm. I'll just re-read this thread before attempting to compose a coherent answer on this part.
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM