Re: --enable-shared doesn't work on Sun-3

[Toon Moene <toon at moene dot indiv dot nluug dot nl>]

  > Note that on my m68k-next-nextstep3 system exactly the same code is  
  > generated, and the native compiler on my system _is_ gas.

>  And it's accepted?  In that case, NeXT must have hacked
>  the assembler.

No, that's why I complained about the (seemingly automagically  
generated) --enable-shared build on m68k-next-nextstep3 in May this  
year.

So, on my system, this code is generated in spite of the fact that:

a. My assembler doesn't know how to deal with it (because it's gas).
b. It's a Sun trick, which should mean it shouldn't be generated
   *at all* on a m68k-next-nextstep3 system.

  > I don't know what to think of this; either:
  >
  > 1. The S[t]un assembler recognises the jbsr aap,a1 construct as
  >    special and generate the right stuff for PIC - then we can't
  >    do nothing here, although Kate could try to use the original
  >    Sun assembler.

> Right.  This is exactly what is happening.

Then it might be advisable to have egcs *not* generate this code,  
except for a m68k-sun-* system, right ? (And generate an error  
message in case someone specifies -fpic on the command line, because  
it can't be dealt with anyhow ;-).

Cheers,
Toon.