This is the mail archive of the
mailing list for the Cygwin project.
Re: git 2.8.3 spurious output
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Wed, 8 Jun 2016 08:32:36 -0600
- Subject: Re: git 2.8.3 spurious output
- Authentication-results: sourceware.org; auth=none
- References: <087DA9770269374FB58D517AC05CCA3F0174977E08 at mbx04 dot nvlsi dot no>
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:
echo "Say 'exit' to leave MinGW shell and restore Cygwin environment."
/bin/bash --rcfile ~/.mingwrc
You also need that ~/.mingwrc file:
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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple