public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon 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, 23 Dec 2022 18:09:20 +0000	[thread overview]
Message-ID: <bug-107998-4-Wl95INtCng@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 #10 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Can you try to revert my patches:
f0d3b6e384a68f8b58bc750f240a15cad92600cd
ccb9c7b129206209cfc315ab1a0432b5f517bdd9
and remove your patch at comment #5 ?
You should still see the problem you reported in bug #108011


However, I don't understand why you had to do what you describe in comment #8.
When multilibs are disabled, the build shouldn't try to use MULTILIB_OPTIONS
etc...

  parent reply	other threads:[~2022-12-23 18:09 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 [this message]
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
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-Wl95INtCng@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).