On Tue, Dec 10, 2002 at 09:45:19AM -0500, Andy Dougherty wrote:
> Obviously, failing to find a freshly-installed module is bad.  However, 
> I'd want to see a precise demonstration of exactly what went wrong before
> coming to any conclusion.

Glad you asked.  Quite by accident, I may have run into the upstream
issue that caused my downstream problem from a month ago.  Here's
what I did:

1) Built & installed a fresh perl5.8.0.  I used the following
    Configure on hpux11.00 (nonstandard noise is due to
    DBD::Oracle considerations):
        Configure -d -Dprefix=$HOME/perltest/ \
          -A prepend:libswanted='cl pthread ' -A prepend:ccflags='+z '

    I should note that lib/ExtUtils/t/Installed.t fails one test
    (line 161) because it assumes $Config{man1direxp} exists (which
    in my case is set to $HOME/perltest/man1dir).  Maybe
    $Config{man1direxp} shouldn't be set to a non-existent dir, or
    maybe Installed.t shouldn't assume a value is an actually a dir,
    but either way it's irrelevant to makemaker issue at hand.  I
    went ahead with the install anyway.
2) Tweaked .profile to put $HOME/perltest/bin at head of PATH, then
    logged in again
3) Ran "perl -V" and saw the following INC:
  @INC:
    /home/jdl/perltest//lib/5.8.0/PA-RISC2.0
    /home/jdl/perltest//lib/5.8.0
    /home/jdl/perltest//lib/site_perl/5.8.0/PA-RISC2.0
    /home/jdl/perltest//lib/site_perl/5.8.0
    /home/jdl/perltest//lib/site_perl
    .
4) Built & installed DBI-1.30.  Here's where an issue occurs: if I
        perl Makefile.PL
    things work great: it installs into
        $HOME/perltest/lib/site_perl/5.8.0/PA-RISC2.0/
    and perl is quite happy to find it.  However, if I
        perl Makefile.PL PREFIX=$HOME/perltest
    then it installs into
        $HOME/perltest/lib/perl5/site_perl/5.8.0/PA-RISC2.0/
    Note the addition of "perl5".  Also note that the same prefix is
    used here as was on the build of perl.  That's the "accident"
    I mentioned: today, I forgot to specify the PREFIX that I
    specified a month ago.

So, it seems the issue is that MakeMaker is adding "perl5" to DBI's
INSTALL settings.  Instead of the previously submitted patch, should
I be submitting a patch for that issue?

I'm unsure, so I'll wait to get your impressions first before
throwing any cycles at it...
-- 
J.D. Laub (Laubster)  |"Your leg's too long / Your skull's too strong /
[EMAIL PROTECTED]| Suppose your nose is wrong." - Renaldo & the Loaf

Reply via email to