Re: Bug#930980: libcrypt-openssl-dsa-perl FTCBFS: configures and builds for the wrong architecture
Hi gregor,
On Mon, Jun 24, 2019 at 06:57:12PM +0200, gregor herrmann wrote:
> On Mon, 24 Jun 2019 10:11:21 +0700, Nguyen Hoang Tung wrote:
> > libcrypt-openssl-dsa-perl fails to cross build because it does not pass
> > cross build tools to configure and to make. Adding
> > /usr/share/dpkg/buildtools.mk lib and re-define linkers and compilers can
> > solve this problem.
If you include (not "-include") buildtools.mk, you must add an
appropriate versioned dependency on dpkg-dev.
> While I like to support improving crossbuildability, I have the
> impression that the issue you address in these 2 patches affects
> hundreds of packages, and that adding boilerplate code to all
> debian/rules files is the wrong approach (and doesn't scale). I guess
> this needs to be tackled at a deeper level, probably the two perl
> buildsystems in debhelper.
I fully agree. I've spared lib*-perl packages thus far, because I think
that they should be fixed at the tooling layer, but I have no clue how
to do that. I was hoping that eventually some perl guy would ask me for
help ...
> Incidentally, Niko look at crossbuilding arch:any perl packages at
> our recent sprint briefly. What I find in our gobby notes is
... or takes it in his own hands. This is great news!
> | implement debhelper support for cross building XS module packages?
> | effectively make debhelper run 'perl -I /usr/lib/<arch>/perl/cross-config-5.28.1 Makefile.PL' when it detects a cross build
>
> which points in the same direction. And I'm sure Niko can add more on
> this topic than I :)
This is quite precisely the information I was missing thus far. I think
the major question now is: Who wants to turn this into a debhelper
patch? The second question is: Why do we need the perl version in that
part? (Can it be renamed to something without the version?) If there is
a reason: How do we compute the correct version?
Getting this into debhelper post-buster has the potential to fix
hundreds of perl packages indeed.
Can I use this opportunity to ask the Debian Perl Group for a favour? If
you want to help with cross building, please annotate any Build-Depends
that are only used for testing (i.e. droppable when
DEB_BUILD_OPTIONS=nocheck) with "<!nocheck>". As maintainers, you'll
have a good intuition for which dependencies are candidates. For
reproducible packages, you can build once with DEB_BUILD_OPTIONS=nocheck
DEB_BUILD_PROFILES=nocheck, then without these vars, and compare the
binary packages to verify correctness of the annotations. Thank you for
your support.
I've added d-cross@ and d-perl@ into the loop and dropped the individual
bugs.
Helmut
Reply to: