From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 1EF233858D37; Tue, 11 Apr 2023 12:03:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1EF233858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681214605;
	bh=/ZwAZXupF6UoxlTiPAoSc/GwbQ3xPiRfnZk+SOxPL5I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=n92z4Jbpo2pRoau+Cd23kG8Xi+9C9yNuqab+E3VJpi8pzCZx37KPaxIwZ+aN1enL4
	 VGV+uQDcHLTphRhmUlvBWmDjVhwlixS+PyDiorHWcX8hJe250KDS2XHnRRVl4yPJfU
	 dPR+zc727vekK4zVRnG2tBsq6tYR79N0HM+acyco=
From: "costas.argyris at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/109460] Build gcc for win32 failed in gcc13 master branch
Date: Tue, 11 Apr 2023 12:03:24 +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: WAITING
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: <bug-109460-4-bHqoIi26lw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109460-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109460-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109460

--- Comment #11 from Costas Argyris <costas.argyris at gmail dot com> ---
As I said before, I think adding the "-o" flag to

$(COMPILER) -c $< -o $@

is a good and harmless change, but, as per your own report, it didn't solve
your issues because you still got that mysterious line:

utf8-mingw32.o: In function `WinMainCRTStartup':

which doesn't make sense to me.    This makes me suspect that the problem is
something else and not the abscence of "-o".    These object files have not=
hing
to do with such main functions that are associated with executables.    So
unless you come up with gcc-specific reproduction steps for me to investiga=
te,
you have to figure out why this object file even has a WinMainCRTStartup
function after adding the "-o" flag.

I also noticed you are using gcc 7.3 as the cross-compiler.    Would it be
possible to use a more recent version, just to see if that makes a differen=
ce?=