Forums

Hi,

Two ideas come to mind:

1. How did you obtain the sources in this case? If you used
CVS and you had a previous (older) copy of the sources in
the same directory (even a prerelease of 3.0), then try
deleting the _wrap.cpp file in the python directory. I'm
afraid there is a bug in the make system that prevents it
from remaking the _wrap.cpp file at the right time based
on the dependencies. This only happens when an older
libsbml_wrap.cpp file is in the directory. If you
downloaded the fresh 3.0.0 sources, this shouldn't be a
problem because the download contains an up-to-date
version of the swig-generated wrapper file.

2. Is it possible your version of swig is older that 1.3.31?
Libsbml's configure program should complain about it and
refuse to continue, but maybe it failed to do that and
let the configuration continue.

Let us know about the above, and we'll try to continue
helping from there.

MH

--
Mike Hucka, Ph.D. mhucka@caltech.edu http://bnmc.caltech.edu
Senior Research Fellow, Control and Dynamical Systems
Co-director, Biological Network Modeling Center (BNMC)
Beckman Institute @ the California Institute of Technology

____________________________________________________________
To manage your libsbml-discuss list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/libsbml-discuss

For a web interface to the libsbml-discuss mailing list, visit
http://sbml.org/forums/

For questions or feedback about the libsbml-discuss list,
contact sbml-team@caltech.edu.