public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100427] canadian compile for mingw-w64 copies the wrong dlls for mingw-w64 multilibs
Date: Wed, 05 May 2021 03:51:10 +0000	[thread overview]
Message-ID: <bug-100427-4-G7ZbJYmFgx@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

--- Comment #1 from cqwrteur <unlvsur at live dot com> ---
I think this is probably the reason why I got the last error, because canadian
cross toolchains install the wrong multilibs for dlls.

I personally suggest libstdc++-6.dll should install in /lib just like Linux or
other POSIX compliant systems are doing. Or of course, it will break multilibs.

Just add /lib or /lib64 to the environmental variable list on windows or in the
registry with wine, it will work correctly and the operating system will find
out the correct dll for both 32bit and 64bit libstdc++-6.dll

  reply	other threads:[~2021-05-05  3:51 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 ` unlvsur at live dot com [this message]
2021-05-05  3:53 ` [Bug libstdc++/100427] " 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
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-G7ZbJYmFgx@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).