🚀 go-pugleaf

Please, anybody who has built libg++-2.3 in a non-standard path, can you tell
me what you did?

I used "config --target=sun3 --prefix=/usr/gnu/gcc-2.3.3 --nfp" prior to making
gcc. Then I used "config sun3 -prefix=/usr/gnu/gcc-2.3.3" prior to making
libg++-2.3. This was after several other unsuccessful attempts at building
the libs, by the way. I couldn't really find an explicit direction for what
prefix to use in any of the REAME's.

I also "set path = (/usr/gnu/gcc-2.3.3 $path)" before trying to make libg++.

Then I get all sort of mysterious errors. For instance:
   In file included from ./../iostream/streambuf.h:27,
      from ./../iostream/iostream.h:24, from ./../iostream/stream.h:7,
      from ./String.h:26, from String.cc:25:
   ./../g++-include/stdarg.h:2: stdarg.h: No such file or directory

I don't get it. File stdarg.h includes stdarg.h, with some comment about:
   #ifndef __GNUC__
   /* Use the system's macros with the system's compiler.
      This is relevant only when building GCC with some other compiler.  */
   #include <stdarg.h>

Since by this time in the process, I am building the libs, not GCC, why
would this be relevant.

By the way, the --nfp was something I only tried the last 2 times I built
gcc. Does anyone know how to tell whether their sun3 has the floating point
unit?


Anyway, if you have built the lib's in a non-standard path, can you tell me
what you did. There must be something I'm missing.

Thanks a lot if you can help.
tim werner
werner@sparcserver.mc.ab.com
--