http://qs321.pair.com?node_id=243730


in reply to Building Perl in a Non-standard environment

Just a shot in the dark, not sure if this is what you want, but check this out:

ExtUtils::MakeMaker Docs

-- Can't never could do anything, so give me and inch, I'll make it a mile.

Replies are listed 'Best First'.
Re: Re: Building Perl in a Non-standard environment
by comand (Acolyte) on Mar 17, 2003 at 18:56 UTC

    I had tried this, but the build still complains that it cannot find perl.h. The perl executable *thinks* it is installed in /usr/local/perl5, but actually there is nothing there. I cannot install into this directory, because I don't have root permission on the ClearCase server.

    What I need is a way to tell the module to use $(dist)/perl5 sub directories for build/install, but still keep internal stuff (like the #! path for LWP scripts) pointing to /usr/local/perl5/bin/perl. Perl lets me do this easily, but I can't figure out how to make the same thing happen using ExtUtils::MakeMaker...

      Well, it's been over 4 years since I used ClearCase, but I vaguely remember having a similar problem. Unfortunately for you, I did have root on the build box, so the solution for me was to make /usr/local/perl5 (and other necessary places) into vob-exported directories (Is that the right term? It used a view to figure out what was there, but you didn't need to be in the view to see it).

      If you can't get root permission, perhaps your sysadms will give you a suid script that installs the (newly built) Perl in /usr/local/perl5/..., which you could then run after building perl but before building extentions.

      HTH,
      --roundboy