Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!news
From: melling@cs.psu.edu (Michael D Mellinger)
Newsgroups: comp.sys.next
Subject: Re: cc -bsd -traditional barfs on std include files (1.0a)
Message-ID: <$w6G$o5m1@cs.psu.edu>
Date: 10 Apr 91 23:46:56 GMT
References: <1991Apr10.022255.17760@menudo.uh.edu>
Sender: news@cs.psu.edu (Usenet)
Organization: Penn State Computer Science
Lines: 20
In-Reply-To: matt@karazm.math.uh.edu's message of 10 Apr 91 02:22:55 GMT
Nntp-Posting-Host: sunws5.sys.cs.psu.edu


In article <1991Apr10.022255.17760@menudo.uh.edu> matt@karazm.math.uh.edu (Matt Emerson) writes:

   Just grabbed a bunch of BSD games off uunet, including warp. Most compiled
   with no fuss, but warp needed cc -bsd -traditional (mainly for old-style
   preprocessor behavior).

   Anyway, stdio.h and ctype.h both elicited parse errors at places where they
   declared something to be const char *, namely fdopen in stdio.h
   and _ctype_[] in ctype.h. I nuked those const's and everything went ok.

   Even "hello, world" wouldn't compile with cc -bsd -traditional. An oversight
   which I trust is fixed in 2.[01].  I guess I ought to try to upgrade before
   OD costs double again.

   Back to playing hangman and robots...especially robots...

This is not fixed in 2.0.  Try cc ... -Dconst="" for a quick fix.

-Mike