This is the mail archive of the
pthreads-win32@sources.redhat.com
mailing list for the pthreas-win32 project.
Re: [Mingw-users] shared libgcc
- To: Hugues Talbot <Hugues dot Talbot at cmis dot CSIRO dot AU>
- Subject: Re: [Mingw-users] shared libgcc
- From: Jeff Sturm <jeff dot sturm at appnet dot com>
- Date: Thu, 14 Dec 2000 22:51:06 -0500
- CC: mingw-users at lists dot sourceforge dot net, pthreads-win32 at sources dot redhat dot com
- References: <200012142342.KAA05846@pyrmont-nh.nsw.cmis.csiro.au>
Hugues Talbot wrote:
> > I do not see any reason why libgcc must always be static. I had never had
> > any trouble with the gcc.dll. If someone cares about create a compiler
> > switch to select between static and shared libgcc.
>
> I've never tried this but isn't the option there already?
>
> gcc-2.95.2 % ./configure --help
> [...]
> * --enable-shared -- Build shared versions of the C++ runtime
> libraries if supported --disable-shared is the default.
--enable-shared in gcc 2.95 and earlier affects the C++ runtime only
(and Java runtime, if built). libgcc is always static.
GCC 3.0 will switch to a shared libgcc, IIRC. It's not perfect but
rather trades one set of problems for another. EH is one of the main
considerations.
I don't know how much, if any, of this is applicable to Win32 however.
Having --enable-shared do the right thing for mingw may require patches,
and it's not clear who is maintaining gcc for mingw these days.
Jeff