This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: assert (! "unexpected dynamic reloc type");

To: Roland McGrath <roland@frob.com>
Subject: Re: assert (! "unexpected dynamic reloc type");
From: Philip Blundell <pb@nexus.co.uk>
Date: Fri, 16 Jul 1999 09:57:20 +0100
cc: GNU libc hacker <libc-hacker@sourceware.cygnus.com>

>Any objections to changing this to use _dl_signal_error with
>a suitably composed message?  

That sounds like a good idea to me.  In the particular case of the problem 
your friend is having, chances are he has some shared object that was built 
without -fPIC, or with a buggy version of GCC that didn't do PIC quite right.
This causes R_ARM_PC24 relocs to leak into shared objects where they can't be 
handled.  I have considered on a couple of occasions adding an explicit error 
message to explain what's wrong, but never got around to it.

p.

References:
- assert (! "unexpected dynamic reloc type");
  - From: Roland McGrath <roland@frob.com>

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]