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 1D7043858289; Tue, 11 Apr 2023 10:12:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1D7043858289
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681207968;
	bh=gbe2CS/A4NnaSCw8NswkapSp53HUnDt56uCeWXfVDnk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PrggWu/zbzASY68s54iXSL2+poD5RMv5eMiTS/eSpsEqvuORjDkfKfGqbP8zpS7gg
	 HsSOUHB3hY3TRG6lRVV0dMEaWPhFs6kKtNWR9Rd5b4Q2zDGyIItLk5PK6xymVoL+l2
	 dTGG2i9pkyq2u4mlXhjnFOQ8VLmdDGLzWhnMljQA=
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 10:12:47 +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-GjKOjVtmKz@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 #10 from Costas Argyris <costas.argyris at gmail dot com> ---
Hi Huaqi,

This is building a larger project, which gcc is part of.    I am not famili=
ar
with that larger project and I have never built it.

Could we extract only the gcc-specific part out of the entire build process,
such that I can reproduce the gcc build failure on its own, just by using g=
cc's
configure?    In other words, I would like to debug gcc's build process onl=
y,
not a larger project's build process which includes building gcc.    If the=
re
is indeed a problem with gcc due to that patch, it should be possible to
isolate it and reproduce it by building gcc only by itself.=