Re: -profile

[Andreas Jaeger]

Mike Castle <address@hidden> writes:

> On Sat, May 05, 2001 at 06:09:02PM +0200, Andreas Jaeger wrote:
> > Mike Castle <address@hidden> writes:
> > > But since -static causes it to succeed, I wasn't sure at what level the
> > > glibc dynamic linker comes into play.  Does it play a role during linking
> > > at all or only during runtime?
> > 
> > libc_p.a is a static library.  The dynamic linker is only used at
> > runtime but has to be noted in the dynamic program.  Might be that
> > here lies the problem...
> 
> The ONLY thing that makes me think it might be a libc problem is that the
> phase where bfd/linker.c ends up with a circular linked list (when it
> should be NULL terminated) involves versioned elements.  Specifically, 
> 
> _bfd_generic_link_add_one_symbol:
> name=__libc_internal_tsd_set, string=__libc_internal_tsd_set@@GLIBC_2.0
> 
> Andreas,
> 
> Can YOU recreate this problem?  Just create a.c with:
> 
> int main(void) {return 0};
> 
> And compile with:
> gcc -profile -lutil a.c

Works for me with gcc 2.95.2 and ld 2.11.90 which is from CVS.

> Do it ever finish for you?  If it does, (and you're using a fairly recent
> ld, which you probably are :-), then I'll assume it's a local problem.  But
> if I can ever get anyone else to recreate this problem, I'll know it's not
> just me.


> (A debian system I have access to has ld 2.9.5.0.37 which works.  The Suse
> system doesn't have profile libraries installed on it... grrrr).

SuSE has it also, you need to install the libraries separatly, they're
in the (in 7.1) glibc-profile package.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj