Benjamin Reed wrote: > Martin Costabel wrote: > >> Another solution would be to run everything on a case-sensitive file >> system, which would un-confuse dyld also. > > Or, I could fix the jython package to use DYLD_FALLBACK_LIBRARY_PATH > instead. :) Didn't realize it was setting that.
Tried that. Doesn't work. The jython error messages are not very explicit; they just say that some library was not found, when in reality it is found but doesn't load for some invisible reason. I think what happens when you don't use DYLD_LIBRARY_PATH is that early on it loads libraries from /usr/lib like libxml2 or libiconv that are later required in their /sw/lib incarnation by /sw/lib/libJavaReadline.jnilib. Some conflict then prevents loading that library, and jython doesn't even start up. It says Exception in thread "main" java.lang.UnsatisfiedLinkError: no JavaReadline in java.library.path although java.library.path is set to /sw/lib, and the library is there. Setting DYLD_FALLBACK_LIBRARY_PATH doesn't change anything. Finding the detailed failure mechanism would need some more debugging. -- Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
