in reply to Adding Modules to Non-Standard Locations in Solaris 8

Setting LIB in addition to PREFIX may be a workaround, but PREFIX alone should be enough. If it isn't, it's either a bug or a sign of an improperly configured perl installation.

From the Extutils::MakeMaker docs:

Conflicts between parameters LIB, PREFIX and the various INSTALL* arguments are resolved so that:
That might sound convoluted on first read, but what it means is that PREFIX *should* set everything, but LIB will override PREFIX should you so desire -- this allows you to send the pods, etc, off to somewhere besides where the actual modules reside.

I've used PREFIX to great effect on many systems, however it *will* break if your perl was not compiled properly. Depending on how the inital locations are defined some of this can end up being hard-coded and beyond the ken of PREFIX.

Matt

  • Comment on Re: Adding Modules to Non-Standard Locations in Solaris 8

Replies are listed 'Best First'.
Re: Re: Adding Modules to Non-Standard Locations in Solaris 8
by beernuts (Pilgrim) on Apr 23, 2002 at 22:55 UTC
    Matt,

    ++. Aside from the compiler changes to Config.pm, Perl is just as it gets installed from the Solaris 8 CDs (which isn't to say it's correct, just standard). What I've found is that setting LIB, INSTALLMAN1DIR and INSTALLMAN3DIR gives me what I'm looking for. Adding PREFIX into the mix seems to confuse MakeMaker. It installs things into strange, recursive-looking directories (../lib/lib/lib, see above post). This seems to contradict LIB overriding PREFIX - it seems to append to it under 5.00503/Solaris 8. Even the dead stock Solaris 8 machine has the same problem. Hrmmmm...

    *heads off to delve into perldoc ExtUtils::MakeMaker*

    Thanks again,
    -beernuts