Re: [PATCH] fmt-merge-msg: avoid open "-|" list form for Perl 5.6

From: Christopher Faylor <me@cgf.cx>
Date: Mar 3, 2006, 00:14 UTC
Message-ID: <20060303001434.GA7497@trixie.casa.cgf.cx>
In-Reply-To: <20060302220930.GE6183@steel.home>

On Thu, Mar 02, 2006 at 11:09:30PM +0100, Alex Riesen wrote:

Show 10 quoted lines

>Shawn Pearce, Thu, Mar 02, 2006 17:55:10 +0100:
>>Maybe I missed this but why are people using the native Windows
>>ActiveState Perl with GIT+Cygwin when Cygwin has a Cygwin-ized Perl
>>installation available?
>
>because the people _can't_ use cygwin's perl.  There are a lot of
>reasons mainly: administrative, perl script incompatibilities and
>cygwin.dll incompatibilities (if you use perl from cygwin, it'll need
>the correct cygwin.dll.  And if a build process uses cygwin tools from,
>for example, QNX Momentics it often comes to clashes).

(Hmm.  I wonder if QNX Momentics is YA GPL violator)

If you have multiple versions of the Cygwin DLL on your system and try to use them all jumbled up together then, yes, you will have problems. This isn't a perl-specific issue. The solution is to put the latest version of your Cygwin DLL in your path (presumably in /bin) and delete all of the older ones.

The newest version is undoubtedly going to be the one downloaded from the Cygwin web site (http://cygwin.com/) but you can get version information from the cygwin DLL by using grep:

  grep -a "^%%% Cygwin" WHEREEVER/cygwin1.dll

if you are not inclined to install the newest version of Cygwin.

I'm sure that there are incompatibilities between ActiveState perl and Cygwin's perl which make it hard to use the same scripts in each so I am not doubting that some people might want to use only ActiveState perl. I don't see how the multiple Cygwin DLL issue can be a problem only for Cygwin perl vs. ActiveState perl.

cgf (who sees a new full-time job looming in the git list)