public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/100427] canadian compile for mingw-w64 copies the wrong dlls for mingw-w64 multilibs
Date: Mon, 26 Dec 2022 15:35:25 +0000 [thread overview]
Message-ID: <bug-100427-4-YmxWsFhlai@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100427-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100427
nightstrike <nightstrike at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nightstrike at gmail dot com
--- Comment #10 from nightstrike <nightstrike at gmail dot com> ---
(In reply to cqwrteur from comment #5)
> I think the copy to bin behavior should be removed. It should be just like
> normal linux distribution. 64 bit dlls in lib. 32 bit dlls in lib32.
This is a feature of Windows. Windows will find dlls in PATH, not in lib
directories.
Multilib toolchains do face issues with versioned runtime libraries. You can
try configuring with --enable-version-specific-runtime-libs. Generally
speaking, it's easier to just build two separate toolchains than to try getting
multilib to work. I made the mistake of pushing for multilib to be enabled by
default, and we never got it working quite well.
Anyway, I don't think this is a bug as stated.
next prev parent reply other threads:[~2022-12-26 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 3:48 [Bug libstdc++/100427] New: " unlvsur at live dot com
2021-05-05 3:51 ` [Bug libstdc++/100427] " unlvsur at live dot com
2021-05-05 3:53 ` unlvsur at live dot com
2021-05-05 3:56 ` unlvsur at live dot com
2021-07-19 14:03 ` unlvsur at live dot com
2021-09-10 10:11 ` unlvsur at live dot com
2021-10-05 0:09 ` unlvsur at live dot com
2021-10-18 4:47 ` unlvsur at live dot com
2021-11-18 1:32 ` unlvsur at live dot com
2021-11-18 9:41 ` [Bug bootstrap/100427] " redi at gcc dot gnu.org
2022-12-26 15:35 ` nightstrike at gmail dot com [this message]
2022-12-26 16:01 ` nightstrike at gmail dot com
2022-12-26 16:03 ` unlvsur at live dot com
2022-12-26 16:03 ` unlvsur at live 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-100427-4-YmxWsFhlai@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).