Front page | perl.perl5.porters |
Postings from March 2000
All,
Ok, I know what's going on. The build default for alpha_osf specifies a
shared libperl.so. A week ago, I successfully built 5.6.0-RC1 and
installed it into /usr/local/* on the Alpha box.
When RC2 (and, later, RC3) appeared, many of the tests failed in bizarre
(and sometimes spectacular) manners. Last evening, I tried building with
a statically-linked perl (libperl.a). Lo and behold, everything worked
properly!
This morning, I discovered that the default behavior of Digi-paq's runtime
loader is to search 'rpaths' (specified at link time) _ahead_ of anything
found in the LD_LIBRARY_PATH environment variable. Since the build
scripts place the final resting place of 'libperl.so' in rpath, the perl
binary in my source directory was alway trying to load libperl.so from
/usr/local/lib/perl5/5.6.0/alpha_osf/CORE - which in this case was from a
different version of Perl! Naturally, once I removed the prior install it
all worked as advertised.
I ran out of time before heading off to work, but it seems we ought to be
placing the string "${LD_LIBRARY_PATH}" at the head of the rpath. If the
documentation is to be believed, this will be interpolated at runtime and
the settings used during 'make test' will preside over the target install
location of libperl.
I think it's important that this be fixed before release, as it is likely
to burn a lot of folks. If nothing has appeared on the list by this
evening, I'll be glad to do it. Spider? Jarkko?
Steve
----------------------------------------------------------------
Steven N. Hirsch tie-line: 446-6557 ext: 802-769-6557
Development Engineer Methodology Integration Team
ASIC Products Group IBM Microelectronics
----------------------------------------------------------------