tv@pobox.com said:
> Actually, it should be building a libgcc_s.so -- that's what other gcc
> targets are using for ths purpose.  (It's PIC, but in the form of a
> linked shared object.)

What are the reasons for a libgcc*.so over a PIC libgcc*.a, besides
space efficiency perhaps?
Wouldn't this mean that the corresponding libgcc*.so must be
distributed together with a shared lib binary, in case the
shared lib is used with code compiled with another compiler
version? (assuming that the code-libgcc interface is subject
to evolution)

best regards
Matthias