Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Thu, 16 Aug 2001 16:40:30 +0200 (CEST)
From:	Karoly Makonyi <makonyi AT pet DOT dote DOT hu>
X-Sender:	makonyi AT petunia DOT atomki DOT hu
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	cygwin g++ 2.95.3 problem at bastring.h
Message-ID:	<Pine.LNX.3.96.1010816163202.1328C-100000@petunia.atomki.hu>
MIME-Version:	1.0

Dear all,

I have read some letter about my problem, but these were reported at the
previous version of the g++ ...


>
>/usr/include/g++-3/std/bastring.h:65: parse error before `>'
>/usr/include/g++-3/std/bastring.h:71: confused by earlier errors, bailing
>out

Mr. Mummit suggested "Simply take the definitions from alloc.h, put those
in malloc.h and delete alloc.h." - at the /usr/include/mingw library. But
there is not alloc.h for me.
I tried use the cygwin with blitz++ when the problem have been coming.

What would be the solution?

Best regards,
	Karoly MAKONYI


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

- Raw text -