From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) by sourceware.org (Postfix) with ESMTPS id A468B3858C2C for ; Mon, 8 Nov 2021 23:18:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A468B3858C2C Received: by mail-qt1-x82b.google.com with SMTP id v4so15340184qtw.8 for ; Mon, 08 Nov 2021 15:18:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=E3qgCuqXA95GDsouAZI1L2iP8TWSTX3GpJWXCQyLfXE=; b=J3QUhH6HqHsOCwm9W89/hhtYMAipE5EtCCckM58l2nUY6RkuCaBZFAgtck6GQxQ29R jWWmtpg/AM1gDcFXb+RWU0+PiCdDPk3fIICPLRh4UlBXr7i4H7RlbCpIgT05e3XBOZpl nzJ7AvJ8cW9f0uPoYBDnqKX92fj/puEDAJEPPdm+vctuZX/7zh0npNYM85gGRIi/avuY Xcjc0peqbWmYAFDqdgpnoj43Nw+lpUhrD1n5zkiiav9KrqYByOW1bB5h8JaVfHEWDvLF O7Y4jZvxWmKL/eYjEnA/EUrB3OVKbioMrql8E3EhOBwML8hD1XJ9XzeWDFV51k1FxAns /Bpg== X-Gm-Message-State: AOAM531QhX7hBnsXlrTN+xPLlDtlFC+x3r69y/hP6PG5TGu9sGYxlrmV vH/I7ZyYZA30e4IkO2crAW4= X-Google-Smtp-Source: ABdhPJxSp/u+7tZhfHsN5X8RZcvm8Ni1Kr3bnF4SMn03IXilugX+boxCAmAKHt4aRASz6P1SZnR5Xw== X-Received: by 2002:ac8:7f83:: with SMTP id z3mr3635276qtj.138.1636413486233; Mon, 08 Nov 2021 15:18:06 -0800 (PST) Received: from smtpclient.apple (047-024-061-100.res.spectrum.com. [47.24.61.100]) by smtp.gmail.com with ESMTPSA id x125sm10306462qkd.8.2021.11.08.15.18.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Nov 2021 15:18:05 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Brian Koontz Mime-Version: 1.0 (1.0) Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot Date: Mon, 8 Nov 2021 17:18:04 -0600 Message-Id: <7601C26F-3ECC-4DC4-930E-D8A7BE3FC10D@gmail.com> References: Cc: cygwin@cygwin.com, ASSI In-Reply-To: To: Adam Dinwoodie X-Mailer: iPhone Mail (18E199) X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2021 23:18:08 -0000 Unfortunately, users don=E2=80=99t always have the time or chops to write wr= appers for missing Cygwin packages or functionality. By its very nature, a C= ygwin environment will always involve non-Cygwin components . In this case, t= he GCM-Core devs are actively working on a Cygwin solution and were able to p= inpoint the cause. I=E2=80=99m a developer too, just not a Cygwin dev. I know what it=E2=80=99s= like being forced to work in a mixed environment. Whenever possible, I pref= er Cygwin packages if they are available. Even then, the environment will al= ways remain mixed. I wouldn=E2=80=99t report a bug I suspected was caused by= the mixed environment. This wasn=E2=80=99t one of those situations. Thanks for all the work you all do with Cygwin. My work would be exponential= ly more inefficient without Cygwin. Brian > On Nov 8, 2021, at 2:50 PM, Adam Dinwoodie wrote: >=20 >=20 >=20 > Cygwin Git is not inherently an appropriate wrapper to allow Cygwin > applications to seamlessly communicate with non-Cygwin Windows > applications. Naively mixing the two will work sometimes, but it's > reasonable to expect problems due to, for example, the fact that a > native Windows application and a Cygwin application will have very > different ideas about the absolute path to a given file. >=20 > In this case, it looks like the change of behaviour was an unintended > side-effect of changes made to the Cygwin DLL, and the folk working on > the DLL have found a way to get things working as expected for Brian. > Nonetheless I agree with Achim, and in general I wouldn't expect the > steps Brian was taking to work reliably anyway. I would expect that, > to get things working within Cygwin's design paradigms, one would need > to either (a) compile GCM as a Cygwin application, (b) not use Cygwin > at all and instead swap to Git for Windows, or (c) write a shim > application that uses native Windows APIs to talk to GCM and > *nix-style Cygwin APIs to talk to Cygwin Git. >=20 > --=20 > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation: https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple