rowdog wrote:
> I just ran into this myself, you need to install the libperl-dev package
> to get libperl.a and the symlink for libperl.so. This is the same as
> Debian and is mentioned in `perldoc perlembed`.

  That's not really the point.

  The point is that running "perl -MExtUtils::Embed -e ldopts" outputs
"-lperl".  That's wrong, because simply linking with -lperl doesn't
work, because it doesn't exist.

  Perl can be updated to check for libperl.a and libperl.so, and output
NOTHING if they're not installed.  Right now, EVERY program that depends
on libperl has to run "perl -MExtutils...".  It then has to double-check
the output, because it may be LYING to you.

  This negates the whole reason to run "perl -M..." in the first place.
 If I have to run stupid autoconf scripts ANYWAYS, then there's no point
in running Perl to see where it's libraries are.

  It would be saner to have the checks all on one place: Perl.  It would
be saner to have perl NOT lie to applications trying to use it.

  If this is an underlying packaging choice by the Debian maintainers,
then they should be forced to write the additional autoconf checks for
every application that needs libperl.

  I'm annoyed not only at the problem, but at the attitude of the
package maintainers who seem to be saying "just step through a bunch of
poorly documented hoops to work around our lying package".

  Alan DeKok.

-- 
libperl.so doesn't exist, and "perl -MExtUtils::Embed -e ldopts" outputs 
"-lperl"
https://bugs.launchpad.net/bugs/120024
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to