X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 412D23858032 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1673790725; bh=zxMhCeCC+U5TH9/VyTL04Sv5fDkztFtSY1Z9mcI7Pnk=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=D6zDX9kQYfyTz+qsDNdwDLlFCe3r0BVxW8WjqJtI7QMg4FEsYLt5oOCi7HTDEp78i 1cO8+QxMGYOORYQCyK6NUHKBV0Heg4nf9Kbd3p7CUwK9HCmw13W4uOeubwkb7DAjCt D5ufp9pudnXJAhoL+Ie9AhuIuvlXWgXEF6vvO9SI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D3EB6385800C 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 AT cygwin DOT com References: Content-Language: de-DE In-Reply-To: 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 X-BeenThere: cygwin AT cygwin DOT 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: , From: =?utf-8?q?Hans-Bernhard_Br=C3=B6ker_via_Cygwin?= Reply-To: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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. -- 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