Re: proposed spec file patch for java / 2.95

[Tom Tromey <tromey at cygnus dot com>]

>>>>> "Jeff" == Jeffrey A Law <law@cygnus.com> writes:

>> However, gcc does not currently search libdir for user-specified
>> specs files.  There is a comment about this in gcc.c, but it isn't
>> very helpful:

Jeff> So, I'm curious, we do search libsubdir and tooldir, right?
Jeff> What mechanism are we using to have those directories searched?
Jeff> Shouldn't we use the same means to specify that libdir should be
Jeff> searched for spec files too.

Jeff> [ Maybe that's what your patch does, if so, say so :-) I get the
Jeff>   feeling that may be what you're doing, a confirmation would be
Jeff>   good.  ]

Yes, that is basially what my patch does.

The function process_command() in gcc.c adds some directories to
startfile_prefixes, including tooldir and libsubdir.

process_command() is called by main() before user spec files are read.
My patch changes main() so that user spec files (*only* those added
via -specs) are read after all the entries are added to
startfile_prefixes.

Jeff> What's the rationale behind having the specfile in the library
Jeff> and not provided by the compiler?

The spec file has to include libraries based on how the library was
configured.  It is much easier for us to maintain the configury for
this sort of thing in a single place -- libjava/configure.in.  If the
spec file was part of the compiler, we would have to duplicate the
configure machinery.  Also you might want to use a single gcj with
different versions of the library (right now there is no reason to,
but there might be in the future).  In this case it makes the most
sense to generate the spec file with the library and the to install
them in the same place.

Tom