From:	"Oliver Brakmann" <obrakmann AT gmx DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: #include <limits>
Date:	Mon, 8 Jan 2001 18:10:50 +0100
Lines:	27
Message-ID:	<93csjg$9gp98$1@ID-32970.news.dfncis.de>
References:	<3A570B97 DOT F3FBA15B AT bigpond DOT com> <9379a7$dv4$1 AT newsg2 DOT svr DOT pol DOT co DOT uk> <3A57BFC6 DOT 19911988 AT bigpond DOT com> <939lkk$31q$1 AT news7 DOT svr DOT pol DOT co DOT uk>
NNTP-Posting-Host:	h2-dial5.privat.kkf.net (212.63.33.132)
X-Trace:	fu-berlin.de 978974129 9987368 212.63.33.132 (16 [32970])
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2014.211
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2014.211
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Stephen Silver wrote...

> so it's a matter of waiting for GCC 3.0 to be released (and ported to
> DJGPP), which is unlikely to happen before March.

How long does it usually take the DJGPP team to do the port of
a new gcc version?

> STLport would probably fix most of the problems, but I haven't heard
> of anyone who has managed to get it to work with DJGPP.

Any idea why that is so? I tried it too, some time ago, without
any success.

Anyway, I thought it _should_ work, considering that STLport
claims to be compilable by gcc 2.95.2 w/o any problems.

Oliver

PS: Sorry, I don't know what error messages I got when I tried to
compile STLport. The first issue that came up was that I had to
turn off something that had to do with pthreads. I remember that
much, but beyond that... :-(

- Raw text -