Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <20020831051418.71006.qmail@web21004.mail.yahoo.com>
Date: Fri, 30 Aug 2002 22:14:18 -0700 (PDT)
From: Nicholas Wourms <nwourms AT yahoo DOT com>
Subject: Re: Gcc 3.2
To: cygwin AT cygwin DOT com
In-Reply-To: <20020831034550.GB18211@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Christopher Faylor <cgf AT redhat DOT com> wrote:
> On Fri, Aug 30, 2002 at 08:16:57PM -0700, Nicholas Wourms wrote:
> >--- Bobby McNulty Junior <bmj2001 AT bellsouth DOT net> 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:
ftp://ftp.gnu.org/gnu/gmp/gmp-4.1.tar.gz

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.

Cheers,
Nicholas

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/