I build each piece in order, installing into a 'dist' subdirectory, which is not the final installation directory. Confused? I am. All of the packages are built as though the installation will be into /usr/local/lib, /usr/local/perl5, but using makefile trickery or Perl Configure's -Dinstallprefix, things are installed into .../myvob/src/dist/lib, .../myvob/src/dist/perl5.
I can manage to get the libraries and Perl itself to install into this directory structure, and have them *think* they ar e installed in /usr/local. The rub is in getting the CPAN modules to build using the 'dist' version of Perl.
For instance, trying to install Config::IniFiles, I get the following error:
Checking if your kit is complete... Looks good Error: Unable to locate installed Perl libraries or Perl source code. It is recommended that you install perl in a standard location before building extensions. Some precompiled versions of perl do not contain these header files, so you cannot build extensions. In such a case, please build and install your perl from a fresh perl distribution. It usually solves this kind of problem. (You get this message, because MakeMaker could not find "/usr/local/pe +rl5/lib/5.8.0/sun4-solaris-64int/CORE/perl.h")
I need the modules to utilize the Perl core stuff from the 'dist' directory, but without building binary dependencies on these paths. This is much the same as the Perl build's -Dprefix vs -Dinstallprefix. I can't figure out how to make Ext::MakeMaker to behave the same way!!!
Any help appreciated.
Edit by tye, change PRE to CODE
In reply to Building Perl in a Non-standard environment by comand
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |