This is the mail archive of the
mailing list for the Cygwin project.
Re: Gcc 3.2
- From: Nicholas Wourms <nwourms at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 30 Aug 2002 22:14:18 -0700 (PDT)
- Subject: Re: Gcc 3.2
--- Christopher Faylor <firstname.lastname@example.org> wrote:
> On Fri, Aug 30, 2002 at 08:16:57PM -0700, Nicholas Wourms wrote:
> >--- Bobby McNulty Junior <email@example.com> wrote:
> >> When will it be an official part of the Cygwin distribution?
> >When Chris is good 'n ready to release it, not a moment sooner.
> I.e., I'll probably release it after I release the next version of
> cygwin since updated headers from 1.3.13 will be required.
> Now, if only I could get "someone" to review the Thomas Pfaff's
> pthread patches...
FYI, if you want to see the problem with gcc-3.2 libstdc++.la
refusing to be linked by libtool, do this:
1)Download gmp-4.1 from:
2)Unpack to a tmp dir, configure with:
"--enable-shared --disable-static --enable-cxx"
3)Run make, and wait till it gets to linking the c++ library, which
will display the message.
At this point it should bomb out complaining that "libstdc++.la is a
static library and Cygwin doesn't allow static libraries in its
shared libraries" [or something to that effect].
Note that this behaviour is seen in a number of packages. Amongst
others, these include Berkeley DB v3+/v4+ c++ libraries and the
plotutils c++ libraries. IIRC, I was encountering the same issue
with compiling setup.exe. This behaviour only occurs with
gcc-3.2(3.1 as well) and has been confirmed on both WinME and Win2k.
I've done my best to figure it out, but I'm not much of a libtool
wiz. It doesn't really seem like a libtool problem, however, because
using CXX="g++-2" & CXXCPP="g++-2 -E" works fine.
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html