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] New: canadian compile for mingw-w64 copies the wrong dlls for mingw-w64 multilibs Date: Wed, 05 May 2021 03:48:15 +0000 [thread overview] Message-ID: <bug-100427-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100427 Bug ID: 100427 Summary: canadian compile for mingw-w64 copies the wrong dlls for mingw-w64 multilibs Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- i find that libstdc++ incorrectly installed 32bit in the $sysroot/bin. Technically, $sysroot/lib or $sysroot/lib64 should install 64bits of libstdc++.dll The code is compiled, but the libstdc++'s dlls are installed incorrectly. cqwrteur@Home-Server:~/all_mingw_toolchains/host/x86_64-w64-mingw32/bin$ objdump -h libstdc++-6.dll libstdc++-6.dll: file format pei-i386 Sections: The actual dll is cqwrteur@Home-Server:~/myhome/glibc231/phase2/gcc/x86_64-w64-mingw32/libstdc++-v3/src/.libs$ objdump -h libstdc++-6.dll libstdc++-6.dll: file format pei-x86-64
next reply other threads:[~2021-05-05 3:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-05 3:48 unlvsur at live dot com [this message] 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 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@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: linkBe 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).