public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Fri, 10 Mar 2023 10:18:53 +0000	[thread overview]
Message-ID: <bug-107998-4-MgHUfSL2ya@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 #23 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Yong <jyong@gcc.gnu.org>:

https://gcc.gnu.org/g:e3f8dfcd885d19d322b10fb4e36d50b60da2576b

commit r13-6578-ge3f8dfcd885d19d322b10fb4e36d50b60da2576b
Author: Jakub Jelinek <jakub@redhat.com>
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 that
    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=
    for i in `${CC-gcc} --print-multi-lib 2>/dev/null`; do
      dir=`echo $i | sed -e 's/;.*$//'`
      if [ "${dir}" = "." ]; then
        true
      else
        if [ -z "${multidirs}" ]; then
          multidirs="${dir}"
        else
          multidirs="${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) multilib
    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  <jakub@redhat.com>

    gcc/ChangeLog:

            PR target/107998
            * config.gcc (x86_64-*-cygwin*): Don't add i386/t-cygwin-w64 into
            $tmake_file.
            * config/i386/t-cygwin-w64: Remove.

    Signed-off-by: Jonathan Yong <10walls@gmail.com>

  parent reply	other threads:[~2023-03-10 10:18 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
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 [this message]
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-MgHUfSL2ya@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).