On Wed, Mar 29, 2000 at 01:53:48PM -0800, Chip Salzenberg wrote: >According to Darren/Torin/Who Ever...: >> A question that came up once before. Would it be better to put >> libperl.so in /usr/lib considering that our Perl binaries aren't >> actually linked with it?
This would have the advantage that the standard shlibdeps mechanisms would work. It does however cause problems if you include libperl.a in archlib/CORE (since the default ldopts includes that directory before /usr/lib). >Well, I think we actually _should_ ship a /usr/bin/perl-5.6-shared >binary. Otherwise, you don't have any way for ... > >> ... MakeMaker and friends ... > >... to find the headers and library and ccflags etc. Shoot, you could >even make perl-5.6-shared a low-priority alternative for perl. All that stuff comes from Config.pm, so shipping a shared binary won't help. You need to include Config.pm from the shared build in -base. Regards, -- Brendan O'Dea [email protected] Compusol Pty. Limited (NSW, Australia) +61 2 9809 0133
