** re-sent as now-again proper member of the mailing list **
Hi,
Randal's problem looks like having one or more of the
following root cases:
- module AutoLoader: sufficiently high version not installed,
or installed twice on your system (installation location
within @INC changed recently, or against the core bundle)
- the same problem applies to Scalar::Util
- IMHO the PAR.pm installation location also changed recently
Hope this helps.
Best regards,
Markus Jansen
>
> > -----Original Message-----
> > From: Eric Wilhelm [mailto:[EMAIL PROTECTED]
> > Sent: Friday, May 11, 2007 2:28 AM
> > To: [email protected]
> > Subject: Re: Hardcoded perl paths --> PAR::Packer failure
> >
> > # from Steffen Mueller
> > # on Thursday 10 May 2007 10:52 am:
> >
> > >Question remains: What's the correct way to fix this? We
> > want to use
> > >the perl that was used to execute Makefile.PL. Additional
> > points for
> > >figuring out how to deal with command line switches.
> >
> > In general, everything on line #1 shouldn't be a problem.
> > That is, anything invoked during build or install will be explicite
> > and any shebang lines in script/ should be getting
> rewritten (I think)
> > by the installer. If not, use Module::Build.
> >
> > The grep results for
> > contrib/automated_pp_test/automated_pp_test.pl do look
> suspicious, but
> > I'm not sure if the bug is coming from there.
> >
> > Randal's specific issue appears to be something in the myldr build,
> > which may actually be an ld -L issue. Do we have more
> information or
> > context available? IIRC, there's nothing in the parl build which
> > would even involve /usr/bin/perl, just /usr/lib/libperl.so.
> >
> > --Eric
> > --
> > A counterintuitive sansevieria trifasciata was once literalized
> > guiltily.
> > --Product of Artificial Intelligence
> > ---------------------------------------------------
> > http://scratchcomputing.com
> > ---------------------------------------------------
> >
