Re: git 2.8.3 spurious output

[Warren Young <wyml@etr-usa.com>]

On Jun 8, 2016, at 8:19 AM, Cufi, Carles wrote:
> 
> So what's the better way of fixing this? Making /mingw/bin/gettext.sh have UNIX line endings or replacing it with the proper Cygwin gettext.sh that I seem to be missing?

Don’t try to mix the Cygwin and MinGW build systems.  Having MinGW in the PATH while developing under Cygwin is one way to make such mistakes, since anything not found under Cygwin falls back to MinGW.

Instead, treat MinGW as a special mode separate from normal Cygwin operation.  MSYS is one way, but I prefer to use Cygwin most of the time, then run a “mingw” script I wrote to temporarily shift my Cygwin environment to MinGW mode:

    #!/bin/sh
    PATH=/cygdrive/c/mingw/bin:/cygdrive/c/windows:\
    /cygdrive /c/windows/system32:/cygdrive/c/cygwin/bin
    echo "Say 'exit' to leave MinGW shell and restore Cygwin environment."
    /bin/bash --rcfile ~/.mingwrc

You also need that ~/.mingwrc file:

    alias make=mingw32-make
    PS1='MinGW: \W \$ ‘

There’s a way to avoid splitting the code between two files, but it would require a slightly more complicated command, so I won’t tell you how.  (If you figure it out, you’ll probably agree that it’s worth splitting the code like this.)

The result is that your PATH temporarily shadows the Cygwin build tools with MinGW ones, excepting for make(1) which is named differently under MinGW, so we have to use an alias instead.

Because this creates a subshell, you can just “exit” to get back out of MinGW mode into Cygwin mode, having never left the directory you were in when you entered MinGW mode.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple