[PATCH] PR bootstrap/10169: Prototype getopt in mips-tfile.c

[DJ Delorie]

> Any suggestions for how to place ../../gcc/include after /usr/include?

I think the right people to think about this problem are the parser
folks (for choosing include paths that make sense) and the fixincludes
folks (for (perhaps) fixing stdio.h but not getopt.h, creating this
type of problem).  I don't know where gcc gets stdio.h on Tru64, but
it might not be /usr/include if it got fixed already.

But fixing this might mean we'll have to be anal about the difference
between <foo.h> and "foo.h" when foo.h is a project-specific header.

> This is out of my league, and I'm concerned about how easy it is to
> break other targets messing with this part of the build machinery.

A valid concern, unfortunately.