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 228673858C1F; Tue, 11 Apr 2023 08:54:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 228673858C1F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681203274;
	bh=q2hB6Q8zWiOAMr1ukzpP2Lkx07NVIkI3xJSkAsRGqBc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hc1TfcbhR5NAXTQ2mZ/xmQerRW/jENsjfUhJptmdyR77zyNR7lVECDZPJDSIhd8Or
	 CQ4uwm6aoxDEAduuvCPvVat+lfepyhyOoHrN8DXK0WU6uQIaHDEnTKXYWxV82oytGg
	 oRne9nGdFtdRL6nTvDXLGziZ3u5+uS6aSbcrixm0=
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 08:54:33 +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-HFZFK6Y7Ih@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 #7 from Costas Argyris <costas.argyris at gmail dot com> ---
Still can't do much without detailed info on how exactly you are building g=
cc,
what is your build setup, what is your cross-compiler version, OS, how you
configure etc etc...    Ideally, solid reproduction steps would be optimal.=
=20=20=20
Also, isolated logs from a single file are not that helpful, could you plea=
se
paste more context from the build log around the error?

Also, is this happening only for the 32-bit windows host, meaning that the
64-bit windows host is succeeding, or you haven't tried the 64-bit windows =
host
at all?

The patch you pointed at has been built successfully with some common build
setups, both cross and native, for both 32 and 64-bit windows hosts, so it
can't be completely broken - we just have to figure out what is different in
your particular build process and is causing problems, which is why I am as=
king
for more info and reproduction steps.

Also, as I said before, the fact that you ended up with this line:

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

indicates that something went horribly wrong because these object files hav=
e no
relation to any main function, and yet they were somehow attempted to be bu=
ilt
as executables.    This should never have happened, so I am curious how exa=
ctly
you ended up in this situation.=