DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 579BoUXC089888 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 579BoUXC089888 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=xv4rhrPd X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 19C8F3857358 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1754740230; bh=lKbGfWs7co7T8sBNCi9OeVCJMI8fP4QnNMl3Cj6x/pE=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=xv4rhrPdf14YgeJXvpDyb0vipPw3uARcFNM54R62hy/3WvIn9ebWfeMNbsM0j9ZWZ ELn/vlLX4NbVUsLsoC0gPr2DONRD3p0wIVAwB24CpP3+H7010mUj4Fc6xpdo3aqdJA N54uKNxqfiqBbOERZs6vkGp/oSsmgHAv8iRSVBiE= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4D8D53858CDB ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 4D8D53858CDB ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754740203; cv=none; b=A13nAG61UgYLbq5uUCfP7BihHRY4k4fKmFWVpWG6u8OAAn7pB7JpjIQbgGOLUudNcnCGHbpAuqv/ptZSD6pc566VwZ2IBtiSy1Bp/3HZ3EI1J66ZwfS08jIRr7lUTMbdj4YL6FQhU2rPNhdDxCh/SHyoxzzJbVgCSgo179tHSAs= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754740203; c=relaxed/simple; bh=sGH3JN6VjBmCAQKbtJA7Q87G3WHM4QwPmmTexJhNj9A=; h=DKIM-Signature:Date:From:Message-ID:To:Subject:MIME-Version; b=d28ZhQnJSAa+mJX4gtKWUX+g/0IVndg8LhBnHklnwLAQdlS8AJiLxshW0WkHLzLf0OwjGmKI8BIR19tzpVFuK69nhWZcJmbhvTZPNZdIbF0JCx7xN9r5Ns7taCur0jjJGJAyzFz1wS/0n1tf5xbga+UmGSJOiGwSqas4oWWeKuQ= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D8D53858CDB X-Yandex-Fwd: 1 Date: Sat, 9 Aug 2025 14:35:07 +0300 X-Mailer: The Bat! (v9.3.4) Professional Message-ID: <706287560.20250809143507@yandex.ru> To: "Old, Oliver" , cygwin AT cygwin DOT com Subject: Re: Incorrect command line handling when launching Cygwin program from Windows In-Reply-To: References: <87264da9-cc87-4a63-89cb-e30fc6c1126b AT emrich-ebersheim DOT de> <1489952594 DOT 20250804215103 AT yandex DOT ru> <4ef0fbf6-8964-491b-984d-1f48bd1aa831 AT SystematicSW DOT ab DOT ca> MIME-Version: 1.0 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Andrey Repin via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Andrey Repin Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Greetings, Old, Oliver! >> NO - its entire purpose is interfacing with Cygwin and other POSIX sosftware, >> including on other systems, from MS cmd if users insist, but according to POSIX >> rules! We now have only limited support for some non-POSIX text files. > I understand. The command line parsing really isn't supposed to offer an > interface for Windows software, but rather "accidentally" works for that > purpose in most cases. Thanks for clearing that up. I'll let my manager > know that anything that goes wrong here is simply because we insist on > being unreasonable (not like I didn't say that before). > Sadly, calling Cygwin binaries from Windows software is somewhat of a > "tradition" in our company. It's all over the place starting with our > classic build procedure: > 1. Fire up a batch script to unpack a Cygwin environment and launch a > shell script in a Bash within the unpacked Cygwin. > 2. Shell script only really calls Make with its given arguments. I'm > guessing that's to ensure the path variable and other environment > variables are set. > 3. The Cygwin Make instance then launches sub-Makes, but those are > spawned from several versions (going back all the way to 3.x) of > MinGW Make that are checked into version control, just like the > tarball of the Cygwin env. > 4. The MinGW sub-Makes are then calling the unpacked Canadian cross- > toolchain hosted in Cygwin (also checked in as tarball). Notice, > we're building on a Windows system for a Linux target. > It's Win32 (cmd) -> Cygwin (bash) -> Cygwin (make) -> Win32 (make) ->> (Win32 (cmd) ->) Cygwin (gcc). > I've always wondered why they had to do quoting in their Makefiles in > such a weird way. > Well, here's to hoping the CMake project system + MinGW toolchains will > be such a resounding success, it'll convince everyone here to stop > misusing Cygwin. If I were you, I'd first removed that hop out of Cygwin. AFAIK, Cygwin provides a mingw cross-compiler, so there's no real need to go out of your way. Also, as a side-note, "unpacking" Cygwin could lead to unexpected and hard-to-diagnoze errors due to sudden changes in DLL space layout. -- With best regards, Andrey Repin Saturday, August 9, 2025 14:32:21 Sorry for my terrible english... -- 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