Hi, Hans Aberg <haber...@telia.com> writes:
> On 3 Mar 2011, at 11:40, Ludovic Courtès wrote: >>>> The crux is that on older MacOS X versions ‘.dylib’ are shared >>>> libraries (not dlopenable), whereas ‘.so’ are “bundles” >>>> (dlopenable). That’s why lt_dlopenext (which is what >>>> ‘dynamic-link’ uses) doesn’t try to open ‘.dylib’ files. >>> The shared libraries (not dynamically loadable, except as when >>> starting up the program like some web browser plugins) were on the >>> PPC platform (XCOFF and PEF I think it was). >>> >>> Now (Mac OS 10.5 and later), all is loadable. Haven't seen any .so >>> files, except as coming from GNU/Linux. >> I would recommend discussing this with the Libtool folks, to see >> how ltdl could adapt to the new situation. > > I recommend that too. - I brought it up a year ago, so if somebody > wants to give it another take, please feel free to do it. :-) It’d boil down to summarizing the situation and proposing a way to detect whether .dylib can be dlopen’d. I don’t have access to OS X, though, so I won’t look into it. [...] >>> UNIX, and the only parts in the UNIX standard recognizing file name >> “UNIX standard”, what a funny phrase! :-) > > Do you like "Single UNIX Specification" better? Sure. :-) Ludo’.
