This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: A difficult question about locale_mutex uninitialized
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: "FCG WANG Baohua" <Baohua dot WANG at alcatel-sbell dot com dot cn>, <gcc-help at gcc dot gnu dot org>, <libstdc++ at gcc dot gnu dot org>, <gcc at gcc dot gnu dot org>, "FCG Ke Yu" <Yu dot Ke at alcatel-sbell dot com dot cn>
- Date: Thu, 7 Sep 2006 20:01:17 +0200
- Subject: Re: A difficult question about locale_mutex uninitialized
- References: <A9DE2BAF233E444FA9C5E77A5825A01E8650F6@ydmail.sbell.com.cn> <20060907113620.caf7edf7.bkoz@redhat.com>
(on-list reply to off-list followup, author stripped by request)
> [Off list]
>
> Doesn't the compiler itself also have to be originally built with thread
> support (one of the magic configure flags)?
Yes. Many of the targets for gcc default to thread support, such as
some of the BSD's and linux.
> Hence to see the thread model (g++ -v test.cpp):
>
> ... yada yada yada ...
> Thread model: posix
> ... yada yada yada ...
Exactly. This is the best way to see if your compiler is configured
correctly.
> So *IF* the compiler (or in this case, the cross-compiler) was built without
> the threading support, *OR* *IF* the libstdc++.a was built without threading
> support... bad things happen.
Yep.
-benjamin