From: Dethe E. <de...@li...> - 2006-12-05 00:07:24
|
On 4-Dec-06, at 3:28 PM, Martin Costabel wrote: > Dethe Elza wrote: > [] >> python [vpython script] >> Which results in: >> Fatal Python error: Interpreter not initialized (version >> mismatch?) >> Abort trap > > Which python does your "python" command run? Is it the same as the > one into whose site-packages directory the visual module was > installed? And the same as used for compiling vpython and boost1.33? /sw/bin/python is the first python in my path and points to /sw/bin/ python2.5 As far as I can tell, it should be the same for all of these cases. > With Fink, if you install for example the python25 package, you > don't get a "python" executable, only "python2.5". You have to > install additionally the "python" package which creates a symlink > between /sw/bin/python2.5 and /sw/bin/python. I already added that symlink manually. Does the python package do more than that? I don't know if I remembered to note this in my earlier mail, but the tip you gave about renaming -lboost_python to /sw/lib/ libboost_python.a worked to get a working VPython, though still crashing frequently. --Dethe "Say what you like about C++, but it's uninitialized variables will always hold a special place in my heart. In a world where we define *everything* concretely it is the last refuge of the undefined. It's the programmer's Wild West, the untamed frontier." --Bjorn Stroustrap |