🚀 go-pugleaf

A few days ago, I posted this bug description:

>There's some sort of include file conflict between libg++ 2.3 and SunOS
>4.1.3.  Here's what I get:

[much deleted]

>gcc -g -O -nostdinc++ -I.. -I. -I./../iostream -I./../g++-include  -c AllocRing.cc
>In file included from ./../g++-include/sys/types.h:15, from /usr/include/unistd.h:72, from ./../g++-include/unistd.h:25, from ./std.h:28, from AllocRing.cc:22:
>/usr/include/sys/types.h:24: conflicting types for `wchar_t'
>./../g++-include/stddef.h:11: previous declaration of `wchar_t'
>*** Error code 1
>make: Fatal error: Command failed for target `AllocRing.o'

After I posted the message, I discovered that there was in fact an
earlier posting from Howard Ferguson <hlf@cerf.net> with much the same
problem described.  I contacted Howard, and he said that Per Bothner
<bothner@cygnus.com> told him to run the following after installing
gcc-2.3.3:

  make install-fixincludes

(per the gcc instructions).  This does indeed fix the problem.  I do
get some warnings here and there.

I always thought the fixincludes step was optional; you could run gcc
with the -traditional flag and you'd be about as well off.  Apparently
this isn't true for libg++.  I wish the libg++ documentation said
something about this!

I also received "me too" queries from:

  Christian.Claveleira@irisa.fr (Christian Claveleira)
  puri-sidd@CS.YALE.EDU (Sidd Puri)

I had an earlier response from Per Bothner, but it was more of a
request for clarification.

BTW, I never saw the original article I posted on Usenet, but it seems
that it made it as far as France.  Odd.
--
J. Porter Clark    jpc@avdms8.msfc.nasa.gov or jpc@gaia.msfc.nasa.gov
NASA/MSFC Flight Data Systems Branch