This is the mail archive of the
mailing list for the Cygwin project.
Re: introduction, fix for npm w.r.t. git, and questions
- From: silverwind <silv3rwind at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 20 Apr 2016 21:30:33 +0200
- Subject: Re: introduction, fix for npm w.r.t. git, and questions
- Authentication-results: sourceware.org; auth=none
- References: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0 at BLUPR03MB230 dot namprd03 dot prod dot outlook dot com> <20160420185011 dot GJ2345 at dinwoodie dot org>
You're on the right track. The root issue is that Node.js (on which npm
runs) is a native Windows binary in pretty much all cases, as it's not
possible to build it or v8 (the JS engine) through Cygwin's toolchain,
at least not without numerous modifications. Node.js had actual support
for Cygwin until 0.4.2 (which is ancient), after which it was dropped,
presumably because of v8 build issues.
I think the "correct" fix would be to get npm (or possibly the
If one were to obtain a Cygwin-built Node.js binary, `process.platform`
would be `Linux` and npm would happily feed POSIX paths into git.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple