🚀 go-pugleaf

In article <9211051454.aa05177@chanel.informatik.uni-kl.de> I write:
> ..some questions..

Thanks to botz@orixa.mtholyoke.edu and wwf@doe.carleton.ca I have
answers to most of my questions.  Hope these answers help someone.

 >1.  Where do the c++ header/include files come from?  I seem

They come from the libg++ distribution.

>2.  Should I be using gas and/or ld?   Benefits?

It's very easy to use the vendor-supplied assembler and loader. 
About the gnu assembler:  I still don't know.
About the gnu loader:     In our (Sun4) case, the sun loader does dynamic
linking, and judging from the notes in the GCC info file, the gnu loader will
not support this in the foreseeable future.  So we'll stick with sun ld.

>3.  The GNU C library (glibc-1.05) is intended for people who have no c
>    library available, correct?  Are there any benefits for folks like us? 

Correct.  Glibc has all ANSI-required lib functions and more, and comes with
a full set of ANSI headers with library function prototypes.  We don't *need*
it because we have the Sun lib, but some of the functions in the GNU libc
may be better and there's a real advantage to using headers with prototypes.

>4.  What is libgcc.a used for?  

libgcc.a contains a bunch of stuff used in linking objects created by GCC.  
There is more related info in the README.X11 that came with GCC.  There
does not seem to be anything in the Makefile to make a shared libgcc.a.
I am still not clear about the implications of this for dynamic linking.

chris...