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 AB864385841D; Thu,  2 Feb 2023 07:05:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AB864385841D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1675321536;
	bh=T0NpDJnMY12fV0J8JDEZ78k2vvrkclbJwmAkQuPpODc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=CV/HTHLsaWRoJ/b3E87Y0+BdkGvlMTKS4qruXSnMsg25pXQ/YLv0RmrLDr56hbHTD
	 I+VRfMWRICb+MlqMjmq95iCuu3CMrO3AEZxirMeKdwAXHSTPtsEiONAUYSxylYHc01
	 tf1pSMXb5TbV9z5AmDjt3WEAoglq7oW6mtPjzbnA=
From: "jakub 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: Thu, 02 Feb 2023 07:05:36 +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: jakub 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-w8S6yZizQr@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 #21 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If so, then I don't understand why does t-cygwin-w64 exist.=