Thank you !

     I apologize - I had stupidly forgotten to start a new console 
window after changing the value of $OCAMLLIB (through 
Start>Settings>Control Panel> System>Advanced : Environment Variables; 
System Variables), so it was still using the path with the 
wrong-direction slashes.  Following your advice (my OCaml install is in 
C:\ocaml3.0.7 and echoing $OCAMLLIB at a bash prompt now gives me 
C:/ocaml3.0.7/lib), findlib 1.0.7 works (afaict) perfectly - ocamlfind 
list gives output, ocamlfind query <packagename> does as well, etc.

     Although it's now clear that your patch + advice worked, I'm 
including the patched configure script (attached) and my $PATH var value 
(below) just in case you can use the data.  May I suggest that you share 
your patch and instructions with Gerd Stolpmann of 
<http://www.ocaml-programming.de> (email <gerd(at)gerd-stolpmann.de>)?  
I think he'd be grateful, as would any other poor souls who want to get 
findlib working on Win32*.

* The MinGW installer, by default (at least on my system), tries to 
place OCaml under the Program Files hierarchy and uses \'s in the value 
for $OCAMLLIB.   Because many, but not all, other Win32 ports of Unix 
tools advise users to avoid spaces in file paths, I went ahead and 
placed OCaml at a location with a space-free path, but I wouldn't have 
otherwise known to change the slashes in $OCAMLLIB's value.

$PATH : 
C:\cygwin\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program 
Files\Common Files\Adaptec 
Shared\System;c:\matlab6p5\bin\win32;C:\Program 
Files\cvsnt;C:\ocaml3.0.7\bin

Thanks again


Eugene Kotlyarov wrote:

> brian donovan wrote:
>
>>     Thanks for your help.  The patch that you attached to your email 
>> works on the configure script for findlib 1.0.4 (current version), 
>> but not on the configure script for findlib 0.8.1 - is it intended as 
>> a patch for 1.0.4?  If, so that's great.  :)  In your advice, I have #1 
>
> Yes this patch is only for 1.0.4
>
>> and #2 covered, the patch, as I said, is applied to v1.0.4's 
>> configure script with no problems, but I hit a snag when I try to 
>> configure.  ./configure and ./configure -mspath both generate an 
>> endless scroll of "dirname : too few arguments" error messages that 
>> only stops when I quit the console window.
>
> This is very strange.
> Can you send me resulting configure script and output of the
> echo $PATH
> command
>
> Also one thing you may try is to find following functions in configure
> script and change comments like shown below. This also requires you to 
> have 'which' command, there is package with such name in cygwin
>
> in_path () {
> #    # Does $1 exist in $PATH?
> #    IFS=":"
> #    for d in $PATH; do
> #    if test -x "$d/$1"; then
> #        IFS="$oldifs"
> #        return 0
> #    fi
> #    done
> #    IFS="$oldifs"
> #    return 1
> #--- The following is not portable enough:
>     if test -x `type -p ls`; then
>     # type -p works!
>         type -p $1 >/dev/null
>     else
>         # use 'which' instead
>         p=`which $1`
>     test -x "$p"
>     fi
> }
>
> get_path () {
> #    IFS=":"
> #    for d in $PATH; do
> #    if test -x "$d/$1"; then
> #        IFS="$oldifs"
> #        echo "$d/$1"
> #        return
> #    fi
> #    done
> #    IFS="$oldifs"
> #--- The following is not portable enough:
>     if test -x `type -p ls`; then
>     # type -p works!
>         type -p $1
>     else
>         # use 'which' instead
>         p=`which $1`
>     test -x "$p" && echo $p
>     fi
> }
>
>
>