Spot on. Thanks Charles - that did the trick (setting WX_CONFIG to point to the right place). I had the universal wxpython installed but unbeknownst to me there was a previous wx installation on my machine. (Possibly installed by some super-pack or along with some other library.) Setting the environmental variable WX_CONFIG to the correct location (/usr/local/lib/wxPython-unicode-2.6.3.3/bin/wx-config) before the build sorted things out.
As an aside, the spurious error messages generated in the build stage (warning: “M_PI” redefined, /usr/local/lib/libgcc_s.10.4.dylib does not contain an architecture that matches the specified -arch flag: ppc, etc.) aren’t helpful and may hide any genuine problems. It would be nice to have them go away.
Thanks again
p
···
After some progress in installing matplotlib (after solving the numpy
problem, thanks), I’ve hit another obstacle. Again, perhaps someone will
recognise the symptoms or suggest the next place to look. The technical set
up: OSX 10.4, MPL 0.87.5, numeric, numarray and numpy 1.0b5 installed,
intel MacBook.
The issue: matplotlib installs but when pylab is imported, I get: :
14:28:56: Debug: ../src/common/object.cpp(224): assert
“sm_classTable->Get(m_className) == NULL” failed: class
already in RTTI table - have you used IMPLEMENT_DYNAMIC_CLASS() twice (may
be by linking some object module(s) twice)?
../src/common/object.cpp(224): assert
“sm_classTable->Get(m_className) == NULL” failed: class
already in RTTI table - have you used IMPLEMENT_DYNAMIC_CLASS() twice (may
be by linking some object module(s) twice)?
Trace/BPT trap
and then dumped to the CLI.
sm_classTableappears to be defined in the
wxagg backend.
Do you have the universal wxpython installed? If so, make sure you
set WX_CONFIG to point to the correct wx-config executable.
–
Dr Paul-Michael Agapow, VieDigitale / Institute of Animal Health
pma@…1244… / paul-michael.agapow@…1245…