[PATCH, v3] Potential solution to librt issue.

Paolo Carlini paolo.carlini@oracle.com
Thu Jul 24 19:07:00 GMT 2008


Hi,

> Thanks, everyone, for pitching in to get this fixed before we
> entrenched the problem.

Yes. I think we are very close to a solution for now good enough.

I'm only still a bit nervous with the inlining (as I was a few days ago in another context): it implies including sometimes <sys/time.h> (hopefully not very often). It implies "unuglified" names like clock_gettime in the header. It implies system-level calls inside the header. I'm still wondering if we could somehow have a mechanism working *inside* the .so, like having clock_gettime considered weak (Martin ;) inside the .so, and then the linking of librt triggering at the end of the linking process if the symbol is actually referenced somewhere in the user code and remained undefined. Is that vague idea clear, does it make sense (I'm asking the experts)?

Paolo.



More information about the Libstdc++ mailing list