Always link against static libgcc on hppa-linux

[law@redhat.com]

 In message <200202150003.g1F03oJg004338@hiauly1.hia.nrc.ca>, "John David 
Anglin
" writes:
 > Simply, binutils needs to be built first before anything else.  If the
 > linker is to automatically link this library with everything, I don't
 > see conceptually that this is significantly different from it adding
 > call stubs or other linker generated code.  I would be concerned about
 > moving the build of the milli routines further back in the build
 > sequence although it may work.  Libgcc depends on the milli routines.
I disagree that this implies that the millicode routines need to be part
of binutils.

First, let's look at a native build.  By definition you already have the
compiler, assembler, libraries, etc.  ie, you're just rebuilding your
distribution.   Clearly you've already got an assembler, so you can 
build and install libmilli.a just fine.

In a cross build the tools don't depend on the target's libmilli.a  So
you can build/install it anytime you please.

If you think about it, the situation for libmilli.a isn't significantly
different than the situation for glibc.


jeff