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++/108027] mcf thread model causes build issues for multilibs of x86_64-w64-mingw32 target
Date: Fri, 09 Dec 2022 04:25:12 +0000	[thread overview]
Message-ID: <bug-108027-4-n7vPS14VR2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108027-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from cqwrteur <unlvsur at live dot com> ---
(In reply to LIU Hao from comment #1)
> I need some information about this though:
> 
> 
> When multilib is enabled, does GCC still link programs with `-lmsvcrt`?
> There seems to be only reference to msvcrt:
> 
>   gcc/config/i386/mingw32.h:187:   -lmoldname -lmingwex -lmsvcrt -lkernel32
> " MCFGTHREAD_SPEC
> 
> which is followed by `MCFGTHREAD_SPEC`.
> 
> 
> If GCC links against libmcfgthread in both m32 and m64, then I suspect there
> is only one issue: You forgot to install mcfgthread. I don't know whether
> libtool has builtin macros for multilib builds; by default libraries are
> installed into `<prefix>/lib` and you have to copy them into
> `<prefix>/lib32` and `<prefix>/lib64`, respectively.

I do install mcfgthread. Yes. I do both of them. The problem is that libtool
will incorrectly link to lib/libmcfgthread.la even lib32/libmcfgthread.la and
lib/32/libmcfgthread.la exist.
Can you just remove the .la file?

  parent reply	other threads:[~2022-12-09  4:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  2:42 [Bug libstdc++/108027] New: mcf thread model causes build issues for x86_64-w64-mingw32 multilibs unlvsur at live dot com
2022-12-09  4:20 ` [Bug libstdc++/108027] mcf thread model causes build issues for multilibs of x86_64-w64-mingw32 target lh_mouse at 126 dot com
2022-12-09  4:25 ` unlvsur at live dot com [this message]
2022-12-09  4:26 ` unlvsur at live dot com
2022-12-09  5:38 ` unlvsur at live dot com
2022-12-09  6:31 ` unlvsur at live dot com
2022-12-09  8:01 ` lh_mouse at 126 dot com
2022-12-09  8:53 ` lh_mouse at 126 dot com
2022-12-09 11:14 ` unlvsur at live dot com
2022-12-11 10:07 ` lh_mouse at 126 dot com
2022-12-11 10:25 ` unlvsur at live dot com
2022-12-11 10:30 ` lh_mouse at 126 dot com
2022-12-11 10:31 ` unlvsur at live dot com
2022-12-11 10:32 ` 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-108027-4-n7vPS14VR2@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).