Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: vesper@kong.gsfc.nasa.gov (Greg Vesper - RMS)
Newsgroups: comp.sys.sun
Subject: Broken C++ under 4.1.1
Keywords: SunOS
Message-ID: <1298@brchh104.bnr.ca>
Date: 16 Jan 91 18:45:29 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 30
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 10, Issue 12, message 10
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

I recently upgraded to 4.1.1 only to find that my Oregon C++ compiler and
the GNU C++ compiler are busted under 4.1.1.  Sun changed the setup of
some header files and now my C++ compilers barf with the following sort of
errors:

> In file included from //usr/include/sys/file.h:41, from
> /source/gnu/libg++-1.37.
> 0/g++-include/sys/file.h:18, from File.cc:27:
> /usr/include/sys/fcntlcom.h:123: warning: `flock' was declared `extern'
> and late
> r `static'
> In file included from
> /source/gnu/libg++-1.37.0/g++-include/sys/stat.h:7, from /
> usr/include/sys/fcntlcom.h:147, from //usr/include/sys/file.h:41, from
> /source/g
> nu/libg++-1.37.0/g++-include/sys/file.h:18, from File.cc:27:
> //usr/include/sys/stat.h:90: conflicting types for `unsigned short int
> umask (..
> .)'

Both compilers are generating similar complaints about multiple
definitions in the sys header files.  Is anyone else having similar
problems??  Does anyone know of any fixes??

I traced through the header files for a while and got nowhere.  It looks
like the POSIX compliance preprocessor commands are screwing up.

Any input would be appreciated.

Greg Vesper (vesper@kong.gsfc.nasa.gov) 301-286-5162