On Mar 5, 2010, at 00:44, Carl Sorensen wrote: > System is OSX 10.5.8. MacBook Pro intel. > > I tried to install opendx on my system using port install opendx. > > It installed a bunch of things and then failed. > > Now my X11 is broken. When I try to start it by typing xterm in a terminal, > I get a popup window "The application X11.bin quit unexpectedly." The > Report contains the following: > > Process: X11.bin [1058] > Path: /Applications/Utilities/X11.app/Contents/MacOS/X11.bin > Identifier: X11.bin > Version: ??? (???) > Code Type: X86 (Native) > Parent Process: X [1057] > > Interval Since Last Report: 1228 sec > Crashes Since Last Report: 12 > Per-App Interval Since Last Report: 0 sec > Per-App Crashes Since Last Report: 12 > > Date/Time: 2010-03-04 23:34:18.003 -0700 > OS Version: Mac OS X 10.5.8 (9L31a) > Report Version: 6 > Anonymous UUID: A5D7B888-3352-404C-A14F-BB196D7A0986 > > Exception Type: EXC_BREAKPOINT (SIGTRAP) > Exception Codes: 0x0000000000000002, 0x0000000000000000 > Crashed Thread: 0 > > Dyld Error Message: > Symbol not found: _gll_noop > Referenced from: > /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL > Expected in: /opt/local/lib/libGL.dylib > > > Clicking on the Relaunch button causes it to start up with *two* xterms, so > apparently something is happening. > > > I have the same problem with fontforge: > > sorensen2:~ Carl$ fontforge > dyld: Symbol not found: _gll_noop > Referenced from: > /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL > Expected in: /opt/local/lib/libGL.dylib > > Trace/BPT trap > > Any suggestions for how I might get these dyld symbols to work right?
Have you set DYLD_LIBRARY_PATH somewhere? If so, unset it. I'm guessing the libGL.dylib that contains the _gll_noop symbol is in /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries, but for some reason your programs are finding the one in /opt/local/lib instead, which is newer and doesn't have that symbol anymore. Setting DYLD_LIBRARY_PATH often causes problems like this and is therefore not recommended. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
