Ben Abbott wrote: [] > Is it possible that the wrong dylib is being loaded at run time? Is there a > way to (safely) test the idea?
The other libstdc++ is loaded because it is pulled in by some of the dylibs liboctinterp-3.3.50+.dylib links to, for example /sw/lib/fltk-aqua/lib/libfltk_gl.1.1.dylib. You can see in which order the dylibs are loaded by running octave as env DYLD_PRINT_LIBRARIES=1 octave Another env variables interesting in this context is DYLD_PRINT_BINDINGS (but its output is enormous). Note that I am not sure that this is really the cause of the crash. It would be interesting to see if others know about crashes that appear when dylibs compiled with different versions of g++ are linked together. -- Martin ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
