Re: [Mingw-msys] Strange path transformation with Emacs

On 5:42:07 pm 2005-07-08 Ralf Angeli <angeli@...> wrote:
> * Earnie Boyd (2005-07-08) writes:
>
> > On 4:19:47 pm 2005-07-08 Ralf Angeli <angeli@...> wrote:
> >>
> >> It looks like the shell regards the colon in the original string
> >> as a path separator and tries to replace it by a semi-colon and
> >> some path prefix.
> >>
> >> This prevents CVS Emacs from being built with mingw32-make.exe
> >> which seems to use MSYS' sh.exe as a shell.
> >>
> >> Can this kind of substitution be inhibited somehow?
> >
> > Yes the windows version of make will try to find an sh.exe on the
> > PATH and use it. Windows also includes the directory where
> > mingw32-make is stored as part of the PATH search. If you ensure
> > that mingw32-make cannot find an executable named sh.exe then
> > mingw32-make will use COMSPEC and .bat files to execute the
> subprocess commands.
>
> Okay, thanks for the hint. After renaming sh.exe I could actually
> build Emacs with mingw32-make.exe. Now I have two questions left:
>
> 1) Will there be a switch similar to --win32 for MSYS' make.exe for
> mingw32-make.exe as well? This would be quite convenient.
>
Not planning on it. Will accept a patch for 3.81 due out soon.
> 2) Does this mean the behavior of sh.exe is correct? This very much
> looks like a bug to me. Maybe if the path separator substitution
> could be inhibited, Emacs could even be built using
> mingw32-make.exe and sh.exe.
>
Sh is correct. The POSIX path separator is : and the WIN32 path separator
is ; and using WIN32 paths with the drive specified as d:/ instead of /d/
is where the rub lies. If the variable is to contain a list of paths then
sh will look for : to satisfy it. However, we may be able to scheme up
something for the native/non-native intercommuncation scenario.
Earnie