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
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C3C1798.7020600@fnxweb.com>
Date: Wed, 09 Jan 2002 10:12:40 +0000
From: Neil Bird <neil AT fnxweb DOT com>
Reply-To: Cygwin <cygwin AT sources DOT redhat DOT com>
Organization: Thales Sensors  (but only on behalf of myself)
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.6) Gecko/20011121
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jean le Roux <jean AT infosat DOT net>
CC: cygwin AT cygwin DOT com
Subject: Re: libstdc++ troubles
References: <20020107185616 DOT A4391 AT infosat DOT net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Around about 01/07/02 16:56, Jean le Roux scribbled ...

> ... I also got a tarball
> of libstdc++-v3 from ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/snapshots/
> and copied that to /usr/include/g++-3/

   That's not going to work, if that's all you did!

   The V3 STL headers are *just* the headers for the STL 
library; you not only need to compile up the STL library itself, 
but, unless you want to play silly wotsits with environment 
variables & gcc spec files, you need to compile up a gcc (g++) 
that uses it.

   Try compiling the latest gcc3; that should give you about 
everything you want (comes with latest STL).  To be safe, 
configure it's --prefix to be /usr/loca/gcc3 or similar so you 
keep the Cygwin gcc 2 safe.

-- 
[neil AT fnx ~]# rm -f .signature
[neil AT fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil AT fnx ~]# exit


--
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/