perl-after-upgrade
Anton Berezin
tobez at tobez.org
Wed Feb 16 03:12:12 PST 2005
On Wed, Feb 16, 2005 at 01:50:56PM +0300, Sergey Skvortsov wrote:
> Mathieu Arnold wrote:
> >+-Le 15/02/2005 22:50 +0100, Anton Berezin a dit :
> >|> I already asked once or twice, but I don't remember why it's bad to just
> >|> : ldconfig -m /usr/local/lib/perl5/5.8.6/mach/CORE ?
> >|
> >| 1. Might break things on 4.X, where there is a "real" /usr/lib/libperl.so
> >| 2. This is a larger cludge than patching up the binaries. :-)
> >
> >So, it worked because I don't have any 4.X with a /usr/bin/libperl.so :-)
> ^^^
> No one have :)
>
> Anyway I think that /usr/lib/libperl.so (on 4.X) must be moved somewhere on
> "use.perl port" (and moved back on "use.perl system").
>
> The reason is incompatibility with mod_perl linked against libperl.so.
There is/was the same problem with plperl. It turned out that the
thing's configure _explicitly_ removes -R/path/to/libperl.so from ld
flags. So what mod_perl needs to do is to stop being too clever and to
start respecting perlembed.
=Anton.
--
The moronity of the universe is a monotonically increasing function. --
Jarkko Hietaniemi
More information about the freebsd-perl
mailing list