On Mon, Jan 09, 2006 at 08:35:07AM -0800, Jonathan wrote: > Joe Orton wrote: > >On Fri, Jan 06, 2006 at 12:05:36PM -0800, Jonathan wrote: > >>LOCAL|NOW and GLOBAL|NOW only changes symbol depth. GLOBAL|NOW and > >>LOCAL|LAZY allows symbol breadth and namespace breadth. I suggest > >>another function, apr_dso_open_ex(), if we want more OS specific > >>options. LOCAL|LAZY, however, is portable in likeness across other > >>supported systems without dlopen(). > > > >Is that true for *all* the supported platforms, Win32, OS/2, Netware, > >OS/390, etc etc? > > Here are some comments: > * Win32 -defaults to private/local, has compile-time definitions for > export/import (if supplied) otherwise run-time import is standard > [I've tested] > * OS/2 - defaults to private/local, compiler option to install > automatic handler ...
Thanks for doing the research. Just to be clear, when you say "compile-time" below, I presume you are talking about the compilation time *of the DSO in question*, right? So the answer to my question is "no", you cannot change the dynamic linker behaviour at run-time in this respect on all platforms? joe
