Bug#950297: libyaml-syck-perl FTCBFS: compiler check too strict

[gregor herrmann]

On Fri, 31 Jan 2020 16:50:44 +0100, gregor herrmann wrote:

> > libyaml-syck-perl has a inc/ExtUtils/HasCompiler.pm that is used for
> > checking whether the compiler can build a loadable module. That fails. I
> > think the failure is to be expected, because a cross compiled object
> > cannot be loaded into the native perl. Once removing the "exit 1;" from
> > Makefile.PL line 11, libyaml-syck-perl cross builds just fine. So it
> > really is just this check.
> > 
> > I'd assume that simply patching it out does not suit well with upstream.
> > After all, they put it there for a reason. Unfortunately, I have little
> > clue how to express a "if cross compiling" in perl. Do you have any idea
> > on how to fix this?
> 
> In my understanding, ExtUtils::HasCompiler is there for situations
> where the presence of a compiler is not guaranteed.
> 
> In Debian, we know that we have a compiler when building packages, so
> the check doesn't bring any advantage, and unless I'm missing
> something we could just patch it out.
> 
> I believe we're already doing this in other packages …
> Found an example:
> https://salsa.debian.org/perl-team/modules/packages/libmoose-perl/commit/27905e9167b8dbe0a9fc290472877ff1b9d68c7f

I've now added an equivalent patch to libyaml-syck-perl.
(And I successfully cross-compiled the package for arm64.)

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Ben Weaver: Ocean ain't blue
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20200204/1fae6ed1/attachment.sig>