Re: What version introduced RTLD_DEEPBIND?

On Fri, 27 Oct 2006 13:39:53 -0400 "Brian J. France" <list@firehawksystems.com> wrote: > >> and I plan on removing it from our internal builds as it causes more > >> problems than I think it fixes (on RHEL only). > > > > Err, that'll break my module. > > > Unless you work at Yahoo!, this will not effect you (our internal > builds == Y!). If you do work at Y! we should take this talk onto > our internal mailing lists. Ah, phew! I didn't quite understand what you meant by "internal builds". > > My module is linked with Heimdal kerberos. I need Heimdal because it > > has proper support for SPNEGO (amnong other reasons). But if PHP or > > any other module is linked with a different Kerberos library (e.g. > > MIT) > > symbol collisions will occur resulting in all sorts of strange > > behavior. > > > Could you do the php_compat.h trick and namesapce functions and link > it statically? This is what PHP does for things like pcre and gd. Actually I failed to mention that I do link statically. To be precise the module is dynamically linked with one big statically lib containing Heimdal's libkrb5 and a half dozen other custom libs. I'm not sure what the "php_compat.h trick" is but I'll keep that in mind (e.g. FreeBSD). > > or > > > > extension.deepbind = mymodule.so > > > Ya, I think the extension.deepbind would be a good options (if I had > time to work on it). On second thought I suppose it should be: extension.nodeepbind = othermodule.so Mike -- Michael B Allen PHP Active Directory SSO http://www.ioplex.com/