X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	jmichae3 AT yahoo DOT com
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Turbo Vision compile problems
Date:	Tue, 25 Mar 2008 15:02:08 -0700 (PDT)
Organization:	http://groups.google.com
Lines:	28
Message-ID:	<7dc33fe4-e88a-4f3d-b91e-1c6a03b3783b@i29g2000prf.googlegroups.com>
References:	<cs6dnVyUg4CvO03anZ2dnUVZ_sednZ2d AT comcast DOT com>
	<47d1a913$0$21924$9b4e6d93 AT newsspool2 DOT arcor-online DOT net> <cvydnaXOnKzHa0_anZ2dnUVZ_saknZ2d AT comcast DOT com>
	<47d30654$0$21931$9b4e6d93 AT newsspool2 DOT arcor-online DOT net> <rY6dnWq_tNXfyU7anZ2dnUVZ_hqdnZ2d AT comcast DOT com>
	<47d458b1$0$25507$9b4e6d93 AT newsspool1 DOT arcor-online DOT net> <e0feb3e2-4106-4828-9570-3e8090bf9611 AT i7g2000prf DOT googlegroups DOT com>
	<80a468cd-0b97-4461-b63c-f0c81545cc41 AT i7g2000prf DOT googlegroups DOT com>
	<14hpt3h213d3r2bj19a5keujfjdsplb9s0 AT 4ax DOT com>
NNTP-Posting-Host:	75.175.40.122
Mime-Version:	1.0
X-Trace:	posting.google.com 1206482528 21347 127.0.0.1 (25 Mar 2008 22:02:08 GMT)
X-Complaints-To:	groups-abuse AT google DOT com
NNTP-Posting-Date:	Tue, 25 Mar 2008 22:02:08 +0000 (UTC)
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	i29g2000prf.googlegroups.com; posting-host=75.175.40.122;
	posting-account=05hOMwoAAAB6R8xtiQKzEljSMzgOhVF1
User-Agent:	G2/1.0
X-HTTP-UserAgent:	Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR
	1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.590; .NET CLR 3.0.04506.648;
	.NET CLR 3.5.21022),gzip(gfe),gzip(gfe)
X-Original-Bytes:	2975
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id m2PMF7Nu025454
Reply-To:	djgpp AT delorie DOT com

On Mar 15, 11:04 pm, Brian Inglis <Brian DOT Ing DOT  DOT  DOT  AT SystematicSW DOT Invalid>
wrote:
> On Sat, 15 Mar 2008 14:19:17 -0700 (PDT) in comp.os.msdos.djgpp,
>
> jmich DOT  DOT  DOT  AT yahoo DOT com wrote:
> >do you think tvision could be brought up to 4.2-3 standards?  usually
> >what the problem is during the compile is a string literal bsing used
> >in a char * and apparently GCC 4.2-3 chokes on it.  I know it's not
> >proper, but wouldn't it be fixed if those were changed to
> >const_cast<char*>("blahblah") instead of "blahblah"?
>
> Try removing compile flags -Werror, -pedantic, and -ansi if used, and
> add -std=c89 to see if that eliminates compile failures.
> The first option mentioned changes all warnings into errors, so all
> warning options used e.g. -W... increase the likelihood of compile
> failures.
> If the code is not GCC clean, you will get some or evan a lot of
> warnings, but unless the code is really bad, as in causing undefined
> behaviour, you should not get compilation failures.
>
> --
> Thanks. Take care, Brian Inglis         Calgary, Alberta, Canada
>
> Brian DOT Ing DOT  DOT  DOT  AT CSi DOT com   (Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
>     fake address                use address above to reply

I specified no compile flags.

- Raw text -