Re: [PATCH, v3] Potential solution to librt issue.

[Paolo Carlini <paolo dot carlini at oracle dot com>]

Hi,

> > What does this imply for your idea? I understand, correct me if I'm 
> > wrong, that not-exporting the symbol, arranging for the call to be 
> > inside an header, would make the issue easier to solve. But then, what 
> > would happen if the user code actually uses now? Would have to be linked
> > on a case-by-case basic to libpthread? 
> 
> Yes, but we could arrange it so that the libpthread linking
> occurs automagically.

Ah, that would be just great! Moving the implementation of now outside the .so, inline in the header is certainly doable, not extremely neat, but good enough for now.

Paolo, can you help us (Chris) with the "automagic" thing?

  Note that adding -lpthread is also automatic
> when you 
> add -lrt; so Chris' patch is only breaking -static, whereas
> in the 
> common case it only affects performance.

Ok, thanks for the clarification. Let's not revert anything from now and proceed incrementally, I think we can see now a way forward.

Thanks,
Paolo.