>OK, time for "Configure script debugging 101" :-).
This is awesome, John!!
Thanks for taking the time... You rock!
>
>>Config.log shows the following:
>>
>>configure:4003: checking for perl5
> >configure:4003: checking for perl
>
[snip]
>If you're just going to concentrate on the perl code, add "exit 0"
>as well. That will stop the script at this point and speed up debugging.
So, just focusing on locating perl version 5, for the moment...
>Now, remove config.cache and rerun ./configure, then look at the log (or
>what comes out on the terminal) and figure out what's going wrong:
>
> * Did LOCSYSPATH have everything you expected it to, in particular,
> /usr/bin?
Yes.
>
> * Did the shell loop properly though all the PATH elements, again, in
> particular, /usr/bin?
It never found a file labelled "perl5"
But, *Yes*, the loop terminated when a match was found on 'perl'.
It matched on a path that came before /usr/bin in the PATH variable.
That path is /usr/local/bin. An instance of 'perl' (sans the
character '5') was found. However, if one runs this instance of perl,
one sees that it is
indeed version 5 (v5.005_03).
>
> * Did the "ls -lL" show a match that should have happened?
Yep!
>
> * Did the script say "Found" but yet it continued to loop?
Yes:
Found "/usr/local/bin/perl"
So, it would appear that the script determines version numbers based
on file names...
I'll go on to use these same strategies to see what is happening with
more important facilities, like file locking, which configure thinks
is non-existent.
dk