Dinner time with a nice bit of red is a great occasion to ponder over this sort of thing.
It turns out that I had added a path to my DYLD_LIBRARY_PATH that held my own stats.so and constants.so . The former must explain why R's stats.so didn't load, the latter why I had similar problems with a Python package. It still bugs me why this was never a problem under 10.3 ... How does R load the .so files in its packages? It looks like even if a full path is specified in the file argument to dlopen(), it gets beaten by whatever there is in DYLD_LIBRARY_PATH. That reeks of something buggy (or interestingly different) in dlopen or whatever call is being used, no? On 09/10/06, René J.V. Bertin <[EMAIL PROTECTED]> wrote: > Well... this may be a red herring after all, but it's an interesting one! > > I still don't understand how this could make a symbol unavailable that > is stored in some sort of internal registry. > ______________________________________________ R-help@stat.math.ethz.ch mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
