From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E0F3D385842A; Fri, 10 Mar 2023 10:18:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E0F3D385842A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678443534; bh=O+9DwIi6hl0x+3o/m5l0I+8oowdz+Vg0GJesUYWe5t0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AyViIkplJxG46Pat82KqEdEQjwcPJPc9LPafm8VNhqlYu8dTjCZFI1i1gofCL7aA8 ifA35ecE/oQGiZd3U0OcVls995g+kKSYHNO9CmrRhQToUIBobanEJpPz4h3IMX5Jmg 9fRAvZqmsBBeRw/27M0wMcGXHWPL2PCvZhgVWfwo= From: "cvs-commit at gcc dot 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, 10 Mar 2023 10:18:53 +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: cvs-commit 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107998 --- Comment #23 from CVS Commits --- The master branch has been updated by Jonathan Yong : https://gcc.gnu.org/g:e3f8dfcd885d19d322b10fb4e36d50b60da2576b commit r13-6578-ge3f8dfcd885d19d322b10fb4e36d50b60da2576b Author: Jakub Jelinek Date: Wed Feb 22 10:25:04 2023 +0100 cygwin: Don't try to support multilibs [PR107998] As discussed in the PR, t-cygwin-w64 file has been introduced in 2013 and has one important problem, two different multilib options -m64 and -m32, but MULTILIB_DIRNAMES with just one word in it. Before the genmultilib sanity checking was added, my understanding is t= hat this essentially resulted in effective --disable-multilib, $ gcc -print-multi-lib .; ;@m32 $ gcc -print-multi-directory . $ gcc -print-multi-directory -m64 . $ gcc -print-multi-directory -m32 $ gcc -print-multi-os-directory ../lib $ gcc -print-multi-os-directory -m64 ../lib $ gcc -print-multi-os-directory -m32 ../lib32 and because of the way e.g. config-ml.in operates multidirs=3D for i in `${CC-gcc} --print-multi-lib 2>/dev/null`; do dir=3D`echo $i | sed -e 's/;.*$//'` if [ "${dir}" =3D "." ]; then true else if [ -z "${multidirs}" ]; then multidirs=3D"${dir}" else multidirs=3D"${multidirs} ${dir}" fi fi done dir was . first time (and so nothing was done) and empty second time, multidirs empty too, so multidirs was set to empty like it would be with --disable-multilib. With the added sanity checking the build fails unless --disable-multilib is used in configure (dunno whether people usually configure that way on cygwin). >From what has been said in the PR, multilibs were not meant to be supported and e.g. cygwin headers probably aren't ready for it. So the following patch just removes the file with the (incorrect) multi= lib stuff instead of fixing it (say by setting MULTILIB_DIRNAMES to 64 32). I have no way to test this though, no Windows around, can anyone please test this? I just would like to get some progress on the P1s we have... 2023-02-22 Jakub Jelinek gcc/ChangeLog: PR target/107998 * config.gcc (x86_64-*-cygwin*): Don't add i386/t-cygwin-w64 in= to $tmake_file. * config/i386/t-cygwin-w64: Remove. Signed-off-by: Jonathan Yong <10walls@gmail.com>=