From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0CD4E3858D39; Wed, 1 Feb 2023 18:28:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CD4E3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675276093; bh=GMwYxMnOpiL5KR6V9/fu3BwGmXf88Ox5Ix7vaRskaYo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XE0kBWGtVK945CQARqs6gvuHsA8dWfxw0mUFYTa48j9LMMhwPRISjNDit4le9OrGD PU+w/W4iqo9w2jpgPV9UXFSnnP2mp3kM3rpvl5czdhRgSmwSclCqH1GjaPUrp255Ne e3AXpZdxZ+MyqtQIyOXQ3a2VK59dNGAsTKBEJ6S8= From: "jakub 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: Wed, 01 Feb 2023 18:28:12 +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: 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 #15 from Jakub Jelinek --- (In reply to James McKelvey from comment #14) > Okay I installed gcc-12, built about 10/29/2022: >=20 > $ g++ -v > Using built-in specs. > COLLECT_GCC=3Dg++ > COLLECT_LTO_WRAPPER=3D/usr/local/libexec/gcc/x86_64-pc-cygwin/12.2.1/lto- > wrapper.exe > Target: x86_64-pc-cygwin > Configured with: ./configure --enable-languages=3Dc,c++ --enable-threads= =3Dposix > Thread model: posix > Supported LTO compression algorithms: zlib zstd > gcc version 12.2.1 20221029 (GCC) >=20 > $ cat gcc/config/i386/t-cygwin-w64 > MULTILIB_OPTIONS =3D m64/m32 > MULTILIB_DIRNAMES =3D 64 > MULTILIB_OSDIRNAMES =3D ../lib ../lib32 >=20 > $ gcc -print-multi-lib > .; > ;@m32 >=20 > $ gcc -print-multi-directory > . >=20 > $ gcc -print-multi-directory -m64 > . >=20 > $ gcc -print-multi-directory -m32 >=20 >=20 > $ gcc -print-multi-os-directory > ../lib >=20 > $ gcc -print-multi-os-directory -m64 > ../lib >=20 > $ gcc -print-multi-os-directory -m32 > ../lib32 That matches what I got from a cross-compiler. I think what is more interesting is where e.g. the libraries in the build or installed tree are. Say on x86_64-linux in the build directory I have find gcc -name libgcc_s.so.\* -o -name libgcc.a gcc/libgcc.a gcc/32/libgcc.a gcc/32/libgcc_s.so.1 gcc/libgcc_s.so.1 What do you get with find gcc -name libgcc_s\*.dll -o -name libgcc.a ?=