Date: Wed, 16 Feb 2005 12:12:09 +0100 From: Anton Berezin <tobez@tobez.org> To: Sergey Skvortsov <skv@protey.ru> Cc: perl@FreeBSD.org Subject: Re: perl-after-upgrade Message-ID: <20050216111209.GF19577@heechee.tobez.org> In-Reply-To: <42132590.1010708@protey.ru> References: <20050214154300.GA22736@leia.lambermont.dyndns.org> <20050215211838.GA67316@heechee.tobez.org> <1977F2B2E4A29902C013A350@[192.168.1.5]> <20050215215008.GB67316@heechee.tobez.org> <A8145B2603D11619057725E5@[192.168.1.5]> <42132590.1010708@protey.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050216111209.GF19577>