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 ?
