From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout03.t-online.de (mailout03.t-online.de [194.25.134.81]) by sourceware.org (Postfix) with ESMTPS id D3EB6385800C for ; Sun, 15 Jan 2023 13:51:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D3EB6385800C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=t-online.de Authentication-Results: sourceware.org; spf=none smtp.mailfrom=t-online.de Received: from fwd79.dcpf.telekom.de (fwd79.aul.t-online.de [10.223.144.105]) by mailout03.t-online.de (Postfix) with SMTP id 868475543 for ; Sun, 15 Jan 2023 14:51:47 +0100 (CET) Received: from [192.168.178.26] ([93.238.126.164]) by fwd79.t-online.de with (TLSv1.3:TLS_AES_256_GCM_SHA384 encrypted) esmtp id 1pH3QD-03Wsvg0; Sun, 15 Jan 2023 14:51:41 +0100 Message-ID: Date: Sun, 15 Jan 2023 14:51:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: GCC doesn't find relative includes when passed paths using backward-slashes To: cygwin@cygwin.com References: Content-Language: de-DE From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-TOI-MSGID: 81cea46b-764e-4f67-bccf-1aaf5a8aa69c X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Am 15.01.2023 um 13:38 schrieb Alexander Grund via Cygwin: > The build system, finding it is running on Windows, will pass paths with > backward slashes to the compiler. And that's wrong. Cygwin is not, for practical intents and purposes, Windows. It just runs on top of it. Yes, backslashed path names do work in some cases on Cygwin (note that in the case at hand, you did have to "" around the name for that to work). But at some point that idea has to be given up to achieve the primary goal of emulating a Unix-like environment. The correct solution thus becomes "Don't do that, then." Fix the build system detection to recognize Cygwin as a type of Unix, and things will almost certainly just work.