> I am nearly ready to commit this patch but I went overboard and had it
> search in mingw and MSYS locations for the program to run (i.e.,
> "/bin/sh").
Since there's no MinGW shell, there's no point in looking in there.
Then it occurred to me that maybe this was a little too
> "product specific" for something like libiberty.
>
> Or should I yank out that code and just search for "sh" along the path?
If a PATH search doesn't turn up the shell then a desperate search
through the registery isn't likely to turn up right shell. While in
other contexts finding any shell might be better than nothing, in this
context, fixing the MinGW build failure, the shell needs to be from the
same "Unix emulation" environment that running the build process.
Ross Ridge
--
l/ // Ross Ridge -- The Great HTMU
[oo][oo] [EMAIL PROTECTED]
-()-/()/ http://www.csclub.uwaterloo.ca/u/rridge/
db //
