linker error with new linker

[Andreas Jaeger]

"John Calcote" <jcalcote@novell.com> writes:

> [...]
> If this assumption is correct, then I believe it's really a good thing
> - we SHOULD use all -fPIC flagged code in shared libraries. But I'm not
> sure why it's become important in this later version of the linker.
>  
> SuSE Linux 10 box - ld is 2.16.91.0.2 20050720 (packaged with gcc
> 4.0.2): works fine.
> [...]

It was always this way on x86-64 - and ia64, s390, ppc.  Just i386
handles shared libs without -fPIC - and even there it's not
recommended.  

It just might be that GCC generated different code than before so that
you now have a relocation where you had a different one before.

Cheers,
Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20060712/d1b9d964/attachment.sig>