* Gary V. Vaughan wrote on Tue, May 22, 2007 at 02:11:03PM CEST: > > I'm wondering how to best warn people who have their project > build rely on RTLD_GLOBAL that what they are doing is inherently > non-portable.
Erm, relying on RTLD_LOCAL is non-portable. Relying on RTLD_GLOBAL is not; after all, dlpreloading offers similar. But also relying on allowing undefined symbols in your link is non-portable. I don't see how you can distinguish cases here reliably, in an automatic way. > At first I thought about having the call to lt_dladvise_global > emit a warning to stderr on first call, but that affects users > as well as developers. > > Now I'm thinking the best we can do is flag it in the release > notes, the NEWS file and the manual. That would be fine. Cheers, Ralf
