From:	"deckerben" <deckerben AT freenet DOT de>
Newsgroups:	comp.os.msdos.djgpp
References:	<3D5U8.94680$GY DOT 32020850 AT twister DOT nyroc DOT rr DOT com> <3d2380b0$0$15197$9b622d9e AT news DOT freenet DOT de> <ag1049$d9v$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
Subject:	Re: ANNOUNCE: thinlib directmedia djgpp library 0.1.1
Date:	Thu, 4 Jul 2002 22:08:37 +0200
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Lines:	18
Message-ID:	<3d24aad6$0$8338$9b622d9e@news.freenet.de>
NNTP-Posting-Host:	213.6.190.196
X-Trace:	1025813206 news.freenet.de 8338 213.6.190.196
X-Complaints-To:	abuse AT freenet DOT de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Usage error, I'd say.  You shouldn't be compiling a C source with the
> C++ compiler.  The error message you got is caused by C++ being
> stricter in some situations than C.  In particular, C++ doesn't allow
> implicit casts to or from pointer-to-void, which C explicitly does.

I wouldn't. I have encountered several instances of source distributions
that 'claim' to compile using GCC but really only work with GPP. I would be
much happier myself if the code compiled using GCC to begin with, but
sometimes I don't have any other choice. But thanks for the clarification,
anyhow.

In this case, there were errors with the .10 port that dissapeared when I
compiled with GPP. I am not sure why i didn't bother to check if GCC worked
with the .11, but it does.

Ben

- Raw text -