From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115289 invoked by alias); 20 Apr 2016 19:30:41 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 115276 invoked by uid 89); 20 Apr 2016 19:30:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:2016042 X-HELO: mail-wm0-f68.google.com Received: from mail-wm0-f68.google.com (HELO mail-wm0-f68.google.com) (74.125.82.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 20 Apr 2016 19:30:38 +0000 Received: by mail-wm0-f68.google.com with SMTP id n3so16499250wmn.1 for ; Wed, 20 Apr 2016 12:30:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=RejE+VI5LuW+1PJYHyckaD6yExZJXI2DHMeQNeoAR+o=; b=Z3aDWVQu2Xp+hEkcCA9lgns/3W0iniK110pn8N6GM7UdXP72SuwMaM/CBBLoDDJDmM m6cLtGkWcaSmRPkVatqsXhvQsLokRquABk1Bz1kADiTGFxR+lN48h1rT6h00f2i70OQe ibQ7A5JXF7aQdNx4WB0xdkhs53MRY0K5RhqVznW4OFj4OA8f5YfmSmIsh9anPM23ydB2 zMuRmzb91MMyMW7c8tvYpUYAXPLUXNZX9tVfqmHVEvOucIWiLkB7te5dpgOti9rc+k9K 3l+UrZT5bAg7vPYBYG1H6WsBp6NfGhOGV2NwouS4NqHN08YlOSCVzaynqqyAtwJCtQVj g1LA== X-Gm-Message-State: AOPr4FXdaqXIm0xI9fUA19aj/23iG7KTTPuSV+//wMzqSvWO2PJDn3a6NCtm0TxJMZe7hA== X-Received: by 10.194.84.100 with SMTP id x4mr11864559wjy.169.1461180635984; Wed, 20 Apr 2016 12:30:35 -0700 (PDT) Received: from [10.8.8.30] (212-197-178-181.adsl.highway.telekom.at. [212.197.178.181]) by smtp.googlemail.com with ESMTPSA id qt3sm7057712wjc.32.2016.04.20.12.30.35 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2016 12:30:35 -0700 (PDT) Subject: Re: introduction, fix for npm w.r.t. git, and questions To: cygwin@cygwin.com References: <20160420185011.GJ2345@dinwoodie.org> From: silverwind Message-ID: <5717D8D9.2030600@gmail.com> Date: Wed, 20 Apr 2016 20:37:00 -0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <20160420185011.GJ2345@dinwoodie.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00532.txt.bz2 > I think the "correct" fix would be to get npm (or possibly the > JavaScript engine itself?) to stop acting as if it's in a Windows > environment 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. 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. Regards, Romain -- 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