🚀 go-pugleaf

Greetings!

Where might someone have precompiled GCC/GDB/etc for System V?

Failing that let me complain about problems in compiling gdb

- Something has decided that, since this is SysV, they'd do
	#define index strchr
  But there's lots of local variables with this name, and at least
  one one data structure which has `index' as one of its tags.

  Most of this was in bfd/.

  Y'all may disagree with the naming practices, but it DID manage
  to become a *standard*.  It wouldn't be hard to go through the
  source one day & convert index()s to strchr()s!!!

- gdb/i386-xdep.c has a `#endif' indented by one character.

- How do you get it to compile with `gcc'?  I ran `configure' and
  the resulting Makefile's wanted to use `cc'.  I could edit the
  Makefile's by hand, but then what's the point of using configure?

  I told configure `i386-att-sysv32'.

- The documentation about `configure' needs work as there's lots of
  interesting things you learn by opening the hood and looking at
  the script.  This is NOT how things should be ..

- There's side comments in a couple places which talk about compilers
  which do COFF encapsulation &c.  It sounds as if the (*&^*&^ GNU
  people do not have direct COFF support in the tools *STILL*!  Despite
  the fact there files with names indicating COFF support...

  So I'm confused over how to get it to work with COFF binaries ..?
  The WHATS.NEW file does imply it should work ...

- There's no PROBLEMS file.

- It crashes while reading in a binary file.  Took a very long time to
  read this in, and the crash was in alloca().  (*sigh*)


Enough to make one look for commercial software ...


<- David Herron <david@twg.com> (work) <david@davids.mmdf.com> (home)
<-
<- During the '80s Usenet's mantra was: "Not all the world's a VAX".
<- During the '90s I hope it becomes:   "Not all the world's DOS (ick)".