Why does config.guess come up with such wacky stuff?

[Robert Lipe]

Joe Buck wrote:
> RJL writes:
> 
> > The Right Thing To Do is to refresh the GCC config.guess with the master
> > copy from autoconf.
> 
> Is there any reason why NOT to do this?  That is, does GCC need its
> own independent config.guess for any reason?

I posit the answer is "no" on both cases, but I defer to those with
wider OS exposure than myself.  Alexandre?

Ironically, GCC having its independent config.guess (and being actively
maintained at the time) was the root of this very problem.  I added one
name scheme for EGCS and the patches were quickly accepted.  Another
name scheme was eventually accepted into the autoconf version some time
later.  This is why different config.guess versions identify UnixWare 7
with different triplets.

> If no one can come with one, then please, let's just do it.

So far, I've heard none.

RJL