Installing from CPAN on Win32

Discussion in 'Perl Misc' started by Michael P. Broida, Sep 10, 2003.

  1. Hi!
    I downloaded a module from CPAN. I want to install it on my system,
    but NOT in the net-wide perl "lib" area; I want it in a subdirectory
    under my home dir until I can verify that it does what I need AND I
    can convince the site admin to install it permanently. So, I can't
    follow the installation instructions EXACTLY; I have to tailor them
    a bit. OK, check the docs on how to do that.

    I did:
    perldoc -q "install a module"
    and perldoc -q "keep my own module"
    and got back some useful looking info.

    The first one basically says to do:
    1) Unpack the source into a temporary area.
    2) perl Makefile.PL
    3) make
    4) make test
    5) make install

    Sounds pretty simple, and the second perldoc search tells me to use
    "perl Makefile.PL PREFIX=<path>" insted of 2) above to make it use a
    local library instead of the site-wide one. Good.

    But when I try that, WITH or WITHOUT the PREFIX arg, it tells me it
    can't find installed Perl. It's looking on the S: drive (my DVD drive),
    but our Perl is installed on a network drive connected to T:. NOTE:
    my PERLLIB env.var. points to the same directory via a UNC path. (I
    think "UNC" is the right term; please correct me if needed.)

    I can run Perl normally, so there's no path problem. Yet, this
    "perl" step fails. After the error, it does tell me:
    Checking if your kit is complete...
    Looks good
    but I don't know if it's just checking the Manifest for the module
    at that point or what.

    Any ideas?

    Michael P. Broida, Sep 10, 2003
    1. Advertisements

  2. Michael P. Broida

    Sisyphus Guest

    Try 'perl Makefile.PL LIB=<path>'.
    See 'perldoc ExtUtils::MakeMaker' for some additional documentation.

    Sisyphus, Sep 11, 2003
    1. Advertisements

  3. I looked there yesterday; LOTS and LOTS of confusing info. :)

    Just now tried using "LIB=" as you suggest, pointing to a new
    subdirectory on C:, but I get the same error: it wants to find
    the Perl installation on the S: drive, but ours is on T: instead.

    Any ideas how to make it see the Perl installation on T:??
    Or why MakeMaker wants to see it on S:??

    Michael P. Broida, Sep 11, 2003
  4. Just some suggestions/questions ...

    Are you _sure_ the drive mappings are correct? Something isn't fouled
    in whatever login script may be launched? Re-map the drive just to be
    And how about your PATH? Is it set properly? Have you tried to
    change it so that the only directories in there are for what you're
    trying to do?
    What do you get when you type 'perl -V'? Is the result from this
    command expected? @INC is what you expect it to be?

    Again, just some suggestions/questions to be answered.

    James Willmore, Sep 12, 2003
  5. No problem. I appreciate any insights.

    Yep, the drive mappings are as expected, and have been for a long time.
    This is Win2K, so there's no "login script" launched when running a Perl
    script; and all my Perl scripts work fine. I use that mapped drive (and
    several others) all day long for other tools as well as Perl scripts.

    The PATH is setup fine; Perl is exactly where expected, and there is no
    other Perl installation at or below any path element before or after that
    one in the PATH variable. I haven't modified the path because there are
    paths to several critical tools in there that I can't remove without
    screwing up all of their functionality (and losing a lot of work time).
    Otherwise, it's set as minimal as I can safely make it.

    "perl -V" says a LOT of stuff. <grin>

    Main info:
    perl5 (revision 5 version 6 subversion 0)
    @INC looks as expected, PERLLIB looks as expected (and fits with @INC
    content. Both show the UNC path that corresponds to my T: mapping.

    "libpth" includes "S:\Perl\lib\CORE" which is the error I mentioned
    earlier: I don't have an "S:" drive.

    Here's one oddity that hasn't hurt my USING perl, but maybe it's a
    problem with trying to install a perl module: Inside of "ldflags"
    for "Linker and LIbraries" (and in "lddlflags" for "Dynamic Linking"),
    there is:
    I don't have an "E:" drive mapped, either, so I don't know why that
    is there. My Perl installation is on the mapped T: drive and not under
    a "Utils" directory at all.

    So, I'm still at a loss as to why Perl (including "perl -V") thinks
    our Perl installation is on S: and won't see the T: installation (that
    SOME of "perl -V" points to).

    Anyway, I've decided to go a different way with the project that started
    this whole thing. I was trying to use Win32::GUI (from CPAN) to setup
    a simple GUI over the main Perl tool. Due to this problem (and because
    we don't have a Java2 compiler handy), I'm building an MFC0-based GUI
    that will kick-off the Perl script to do the real work. Thus, we can
    just let this thread die out, unless you have some further insight into
    the whole thing. :)

    Thanks for the inputs!
    Michael P. Broida, Sep 15, 2003
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.