From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AE3983858C5E; Mon, 10 Apr 2023 21:41:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE3983858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681162919; bh=xZaNMzz4Js2Ht5/DoRpbQnjc5YnxMqsIHymVePuP1lY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MQDAKAxN2Lh4zia5NFiDgxjyS50uykk3ZctcgBClisH4/sSfXA0H/9ArpQmJ7Ad6e HBEM3WOwBoewT+65keZ3M7BpSYNfP+S2RzXRJRcgHWhpYdew2qyeKhOAOA5qAbxIGD pAJqdnmTGuGAZSumQ3dk85qtF3SyNWI04rB751A0= From: "costas.argyris at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109460] Build gcc for win32 failed in gcc13 master branch Date: Mon, 10 Apr 2023 21:41:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: costas.argyris at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109460 --- Comment #3 from Costas Argyris --- "The missing -o looks genuine, does not it?" Not to me because this has been built successfully before. If this was t= he problem then it would never build, right? What happened in this case was that sym-mingw32.o was treated as an input to the compiler (see "No such file or directory" error) rather than as an outp= ut which it really is. I suspect this had to do with -fno-PIE triggering building an executable, w= hich I still don't know where it is coming from and whether it should be used for compiling this file, as this has nothing to do with an executable - we are = only compiling the .cc file to a .o file. Still I think it is important to have details of the overall build process followed to get some context.=