🚀 go-pugleaf

I tried compiling gdb 3.5 on our Pyramid98X without
success.    

BTW, config.gdb expected files named "pyramid-<mumble>" rather
than "pyr-<mumble>" as provided in the distribution.

I tried both gcc 1.36 and the native C compiler, but I 
got similar error messages during the final link:

---

rm -f init.c
./munch  main.o blockframe.o breakpoint.o findvar.o stack.o source.o  values.o eval.o valops.o valarith.o valprint.o printcmd.o  symtab.o symmisc.o coffread.o dbxread.o infcmd.o infrun.o remote.o  command.o utils.o expread.o expprint.o pinsn.o environ.o version.o  copying.o  core.o inflow.o dep.o > init.c
cc -I.  -g  -o gdb init.c main.o blockframe.o breakpoint.o findvar.o stack.o source.o  values.o eval.o valops.o valarith.o valprint.o printcmd.o  symtab.o symmisc.o coffread.o dbxread.o infcmd.o infrun.o remote.o  command.o utils.o expread.o expprint.o pinsn.o environ.o version.o  copying.o  core.o inflow.o dep.o readline/libreadline.a obstack.o   malloc.o -ltermcap 
Undefined:
_alloca
_reg_stack_offset
_last_frame_offset
_global_reg_offset
*** Exit 1

---

I believe the missing _alloca was not a problem for the compile with
gcc 1.36, but the other symbols were still missing.  

Also, what does it mean that "GDB on Pyramids works only with GCC",
as stated in config.gdb?  Does that mean it must be compiled with 
gcc, or that output from, say, g++, is not debuggable?


-- Paul Steckler