public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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: Wed, 01 Feb 2023 18:28:12 +0000	[thread overview]
Message-ID: <bug-107998-4-G6XvMm0Jhd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107998-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998

--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to James McKelvey from comment #14)
> Okay I installed gcc-12, built about 10/29/2022:
> 
> $ g++ -v
> Using built-in specs.
> COLLECT_GCC=g++
> COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-cygwin/12.2.1/lto-
> wrapper.exe
> Target: x86_64-pc-cygwin
> Configured with: ./configure --enable-languages=c,c++ --enable-threads=posix
> Thread model: posix
> Supported LTO compression algorithms: zlib zstd
> gcc version 12.2.1 20221029 (GCC)
> 
> $ cat gcc/config/i386/t-cygwin-w64
> MULTILIB_OPTIONS = m64/m32
> MULTILIB_DIRNAMES = 64
> MULTILIB_OSDIRNAMES = ../lib ../lib32
> 
> $ 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

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
?

  parent reply	other threads:[~2023-02-01 18:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 23:25 [Bug c++/107998] New: " mckelvey at maskull dot com
2022-12-06 23:33 ` [Bug c++/107998] " mckelvey at maskull dot com
2022-12-06 23:37 ` mckelvey at maskull dot com
2022-12-07  0:07 ` [Bug target/107998] " pinskia at gcc dot gnu.org
2022-12-07  7:36 ` clyon at gcc dot gnu.org
2022-12-07 16:19 ` mckelvey at maskull dot com
2022-12-10 16:40 ` clyon at gcc dot gnu.org
2022-12-10 18:15 ` mckelvey at maskull dot com
2022-12-10 21:09 ` mckelvey at maskull dot com
2022-12-21 13:27 ` rguenth at gcc dot gnu.org
2022-12-23 18:09 ` clyon at gcc dot gnu.org
2022-12-23 21:22 ` mckelvey at maskull dot com
2023-02-01 17:27 ` jakub at gcc dot gnu.org
2023-02-01 17:55 ` jakub at gcc dot gnu.org
2023-02-01 18:22 ` mckelvey at maskull dot com
2023-02-01 18:28 ` jakub at gcc dot gnu.org [this message]
2023-02-01 18:38 ` mckelvey at maskull dot com
2023-02-01 18:59 ` jakub at gcc dot gnu.org
2023-02-01 19:12 ` mckelvey at maskull dot com
2023-02-01 19:34 ` jakub at gcc dot gnu.org
2023-02-02  6:51 ` 10walls at gmail dot com
2023-02-02  7:05 ` jakub at gcc dot gnu.org
2023-02-21 16:12 ` jakub at gcc dot gnu.org
2023-03-10 10:18 ` cvs-commit at gcc dot gnu.org
2023-03-10 10:30 ` jakub at gcc dot gnu.org
2023-03-14  0:56 ` mckelvey at maskull dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107998-4-G6XvMm0Jhd@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).