From: David R. M. <dr...@fi...> - 2007-02-28 20:00:59
|
On Feb 28, 2007, at 10:23 AM, aaron bryden wrote: > oops meant to send this to fink-beginners also > > ---------- Forwarded message ---------- > From: aaron bryden <br...@cs...> > Date: Feb 27, 2007 2:59 PM > Subject: Re: [Fink-beginners] pymol, libpng problems > To: "Daniel E. Macks" <dm...@ne...> > > > Thanks for your help. > >> I just compiled pymol-py24-0.99-4 and don't see any of my initial >> flag >> suspicions. So here are some pieces of info that could help us >> nail it >> down: >> >> What specific version of which pymol package are you using? What OS X >> version, what CPU type? Which x11 are you using (Apple's X11, Fink's >> xfree86, or Fink's x.org)? > pymol-py24 .99-1002 > OS X version: 10.4.8 > cpu type: 2GHz Intel Core Duo > Apple's X11 version = X11 1.1.3 - XFree86 4.4.0 > I should add that I am using unstable because pymol is not > available for intel >> >> Is this package being compiled on your machine or is it downloaded >> precompiled? If it's being compiled locally, could you tell us the >> command that created that _cmd.so file (it's the one that contains >> "-o >> modules/pymol/_cmd.so", about 6/7 of the way through the build >> output). > The package is being compiled on my machine. The output of the command > to build _cmd.so is > > cc -bundle -bundle_loader /sw/bin/python2.4 -flat_namespace -undefined > suppress -o modules/pymol/_cmd.so */*.o ov/src/*.o -no-cpp-precomp > -Wmissing-prototypes -Wno-long-double -O3 -funroll-loops > -fomit-frame-pointer -ffast-math -I/sw/include > -I/sw/include/python2.4 -I/sw/include/python2.4/Numeric > -I/usr/X11R6/include -D_HAVE_LIBPNG -D_PYMOL_MODULE -D_PYMOL_NUMPY > -D_PYMOL_FINK -L/sw/lib -L/usr/X11R6/lib -lglut -lGL -lGLU -lpng > -lz -lm -lX11 -lXext >> >> Also, the output of these commands: >> >> otool -L /sw/lib/pymol-py24/modules/pymol/_cmd. > otool -L /sw/lib/pymol-py24/modules/pymol/_cmd.so > /sw/lib/pymol-py24/modules/pymol/_cmd.so: > /sw/lib/libfreeglut.3.dylib (compatibility version 12.0.0, > current version 12.0.0) > /usr/X11R6/lib/libGL.1.dylib (compatibility version 1.2.0, > current version 1.2.0) > /usr/X11R6/lib/libGLU.1.dylib (compatibility version 1.3.0, > current version 1.3.0) > /sw/lib/libpng.3.dylib (compatibility version 16.0.0, current > version 16.0.0) > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current > version 1.2.3) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current version 88.3.4) > /usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, > current version 6.2.0) > /usr/X11R6/lib/libXext.6.dylib (compatibility version 6.4.0, > current version 6.4.0) > /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, > current version 1.0.0) > > >> otool -L /sw/lib/libpng.3.dylib > otool -L /sw/lib/libpng.3.dylib > /sw/lib/libpng.3.dylib: > /sw/lib/libpng.3.dylib (compatibility version 16.0.0, current > version 16.0.0) > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current > version 1.2.3) > /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, > current version 1.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current version 88.3.4) >> locate libpng.3.dylib > locate libpng.3.dylib > /Applications/Frozen-Bubble.app/Contents/Frameworks/libpng.3.dylib > /sw/lib/libpng.3.dylib OK, so I've just verfied that Frozen-Bubble-1.0.0e does indeed install libpng.3.dylib as a framework, and running otool on this gives otool -L /Volumes/Frozen-Bubble/Frozen-Bubble.app/Contents/ Frameworks/libpng.3.dylib /Volumes/Frozen-Bubble/Frozen-Bubble.app/Contents/Frameworks/libpng. 3.dylib: @executable_path/../Frameworks/libpng.3.dylib (compatibility version 3.0.0, current version 3.0.0) @executable_path/../Frameworks/libz.1.dylib (compatibility version 1.0.0, current version 1.2.2) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1) So it sounds like this may indeed be the offender, but why does DYLD find it? -- Dave |