public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/105507] Ada build fails for 32bit Windows
Date: Wed, 18 May 2022 22:26:18 +0000	[thread overview]
Message-ID: <bug-105507-4-ngOhBGtvGl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105507-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> So the rule of thumb is to never use -static-libgcc if you have a
> GCC-compiled DLL in the link, that's guaranteed to break otherwise.

So this could happen to the compiler if it is linked with the shared version of
GMP, MPFR or MPC.  Is that the case in your setup?

  parent reply	other threads:[~2022-05-18 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 15:23 [Bug ada/105507] New: " reiter.christoph at gmail dot com
2022-05-17 18:28 ` [Bug ada/105507] " reiter.christoph at gmail dot com
2022-05-18 19:47 ` reiter.christoph at gmail dot com
2022-05-18 20:09 ` ebotcazou at gcc dot gnu.org
2022-05-18 21:02 ` reiter.christoph at gmail dot com
2022-05-18 22:05 ` ebotcazou at gcc dot gnu.org
2022-05-18 22:26 ` ebotcazou at gcc dot gnu.org [this message]
2022-05-19  6:40 ` reiter.christoph at gmail dot com
2022-05-19  9:46 ` ebotcazou at gcc dot gnu.org
2022-05-19 16:14 ` reiter.christoph at gmail dot com
2022-05-19 16:55 ` ebotcazou at gcc dot gnu.org
2022-05-22 15:14 ` reiter.christoph at gmail 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-105507-4-ngOhBGtvGl@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).