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 E68DF3858289; Fri, 23 Dec 2022 18:09:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E68DF3858289
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1671818961;
	bh=lEH3E0X1n+t3GEH6CP1qb2rtTvo6P2mI/zy0+lJGJEo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Ro6YetLN8c9epWQqlPE7Tf3TeP141yxCYCWZUih4iyUh2GPvST1UGTW2IJVCrhrYd
	 hCxoF0wkO2JwBRs13fKJTX4tS2jt0Nvh8XebOngjYcqwonZWBGaOLKU6YfuvMvDj09
	 flVGlDlmIs36rWrCNFVx7gyIbqnkDyNgiTNLeecU=
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107998] [13 Regression] gcc-13-20221204 failure to build
 on Cygwin No dirname for option: m32
Date: Fri, 23 Dec 2022 18:09:20 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107998-4-Wl95INtCng@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107998-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=3D107998

--- Comment #10 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Can you try to revert my patches:
f0d3b6e384a68f8b58bc750f240a15cad92600cd
ccb9c7b129206209cfc315ab1a0432b5f517bdd9
and remove your patch at comment #5 ?
You should still see the problem you reported in bug #108011


However, I don't understand why you had to do what you describe in comment =
#8.
When multilibs are disabled, the build shouldn't try to use MULTILIB_OPTIONS
etc...=