🚀 go-pugleaf

The WHATS.NEW file in libg++-2.1/libg++ implies that you can configure
libg++ to use either the old or new streams code.  For a project I
have, we need the old streams code while we port things over.
However, I do what the following paragraphs state and it doesn't work
because (a) CFLAGS passed to the old-streams make are wrong, and then
(b) once you get them right, gcc -c fails because _IOAPPEND is not
defined.

    --------------------[ WHATS.NEW excerpt ]--------------------
    *** Changes in libg++ version 2.0:
    
    * iostream classes
    
    The major change is that input/output uses the new iostream library.
    The design is based on (but not identical to) iostreams from
    AT&T C++ release 2.x, and the ANSI X3J16/WG21 draft C++ standard.
    
    The iostream classes replace the old stream.  The new
    package provides some compatibility hooks.  Including the
    obsolete <stream.h> (or defining _STREAM_COMPAT) makes 
    more obsolete methods and features available.  However,
    you will probably have to change your code if you have used
    any libg++-specific extensions (such as the File class).
    
    If you want stick with the old stream classes, change the
    definition of IO_DIR in Make.defs (to old-stream).  You will
    also need to 'make depend' in directories that contain depend,
    and then re-configure everything.  Note that the old-stream
    classes are *not* supported and *will* go away in a future release.
    --------------------[ WHATS.NEW excerpt ]--------------------

Has anyone built libg++ 2.1 successfully to use the old-streams?  I am
running a Sun-4 and SunOS 4.1.2 (``configure -target=sun4-sunos4.1'').

Please e-mail responses and I will summarize if the interest is there.
---
Walter Rowe, System Administrator
Robot Systems Division, NIST
<rowe@cme.nist.gov>