Bug#492815: bogus dependencies when building pelr modules, missing dependency in libperl-dev

Marc Lehmann schmorp at schmorp.de
Fri Nov 5 18:47:18 UTC 2010


On Thu, Nov 04, 2010 at 11:45:34PM +0200, Niko Tyni <ntyni at debian.org> wrote:
> No. The libperl-dev package only contains /usr/lib/libperl.so and
> /usr/lib/libperl.a, and only depends on perl and libperl5.10. It is not
> related to building XS modules. Its description reads
> 
>  Files for developing applications which embed a Perl interpreter and
>  for programs compiled with perlcc.

All the agruments are true for embedding too, of course - you need to link
against the same libraries whether you build a module or link in perl, i.e.
if perl says you need to link against -lpthread then in general you need to
do so when embedding as well.

I know older versions of perl just munged all libraries together, which is
how -lgdbm etc. probably ended up (if you build 5.8 this still happens,
Configure asks you which libraries to link against and automatically adds
-lgdbm for the benefit of the GDBM_File module).

> We don't offer a shortcut for pulling in the tools needed to install
> modules outside the Debian package system, unless that shortcut is
> considered to be the 'build-essential' package.

At the moment that's sane. I would argue that back when you had to link in
-lgdbm and others (which were not actually needed, but perl's Config told
apps to require them), this made it rather annoying to use debian for perl.

It's different now, and unless the bug comes back, it's fine as it is.

-- 
                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_              http://www.deliantra.net
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schmorp at schmorp.de
      -=====/_/_//_/\_,_/ /_/\_\






More information about the Perl-maintainers mailing list