[CIG-SHORT] pylith error
Christopher DiCaprio
dicaprio at gps.caltech.edu
Wed Sep 26 16:11:09 PDT 2007
Removing the errant directory and rebuilding proj and spatialdata
with the datum shifts has fixed it. My build of pylith now works!
I get a few errors when running spatialdata pytests, perhaps related
a problem with cppunit.
Thanks to all the developers for their help.
Cheers,
Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pytests.log
Type: application/octet-stream
Size: 9083 bytes
Desc: not available
Url : http://geodynamics.org/pipermail/cig-short/attachments/20070926/9ce87364/pytests-0001.obj
-------------- next part --------------
On Sep 26, 2007, at 3:14 PM, Leif Strand wrote:
> Chris,
>
> Delete the directory 'spatialdata-0.3.0-py2.4.egg' under 'site-
> packages'. It isn't supposed to be there (it may have been created
> if spatialdata's 'setup.py' was run directly). There should be two
> spatialdata-related directories under 'site-packages', as follows:
>
> spatialdata
> spatialdata.egg-info
>
> --Leif
>
>
> Christopher DiCaprio wrote:
>> I've added the --enable-pythia flag and redone configure; make;
>> make install. geocoordsmodule.so now exists in $PREFIX/lib/
>> python2.4/site-packages/spatialdata/geocoords/
>> I added the files from proj-datumgrid-1.3.zip to $PREFIX/share/proj.
>> The libtests (does it know to look for the datum shifts in $PREFIX/
>> share/proj?) and pytests still fail. I've attached the output.
>> Does pylith link statically to anything in spatialdata or is it OK
>> to not rebuild pylith?
>> On the up side this works, which didn't before:
>> ---------------------------------------------------------------------
>> --------------- klaki:~> pylith --help
>> component 'pylithapp'
>> properties: help, help-components, help-persistence, help-
>> properties, job, launcher, mesh_generator, nodes, petsc, problem,
>> scheduler, typos, weaver
>> facilities:
>> job,launcher,mesh_generator,petsc,problem,scheduler,weaver
>> For more information:
>> --help-properties: prints details about user settable properties
>> --help-components: prints details about user settable facilities
>> and components
>> ---------------------------------------------------------------------
>> --------------- Unfortunately, it still fails when I try to run a
>> model:
>> ---------------------------------------------------------------------
>> ---------------------------------------------------------------------
>> ------------------------------ klaki:examples/twocells/twotri3>
>> pylith dislocation.cfg
>> Traceback (most recent call last):
>> File "<string>", line 1, in ?
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pythia-0.8.1.4-py2.4.egg/pyre/schedulers/__init__.py",
>> line 53, in jobstart
>> kwds = kwds)
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pythia-0.8.1.4-py2.4.egg/pyre/applications/__init__.py",
>> line 41, in start
>> shell.run(**kwds)
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pythia-0.8.1.4-py2.4.egg/pyre/applications/Shell.py",
>> line 139, in run
>> method(*args, **kwds)
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pythia-0.8.1.4-py2.4.egg/pyre/applications/
>> SuperScript.py", line 47, in execute
>> self.subscript = self.createSubscript(subscriptName)
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pythia-0.8.1.4-py2.4.egg/pyre/applications/AppRunner.py",
>> line 25, in createSubscript
>> cls = loadObject(name)
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/merlin-1.3.egg/merlin/__init__.py", line 2707, in loadObject
>> obj = __import__(module, globals(), globals(), ['__name__'])
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/PyLithApp.py", line 20, in ?
>> class PyLithApp(Application):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/PyLithApp.py", line 27, in PyLithApp
>> class Inventory(Application.Inventory):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/PyLithApp.py", line 50, in Inventory
>> from pylith.problems.TimeDependent import TimeDependent
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/problems/TimeDependent.py", line 20, in ?
>> from Problem import Problem
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/problems/Problem.py", line 22, in ?
>> class Problem(Component):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/problems/Problem.py", line 31, in Problem
>> class Inventory(Component.Inventory):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/problems/Problem.py", line 51, in Inventory
>> from pylith.materials.Homogeneous import Homogeneous
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/Homogeneous.py", line 22, in ?
>> class Homogeneous(ObjectBin):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/Homogeneous.py", line 31, in Homogeneous
>> class Inventory(ObjectBin.Inventory):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/Homogeneous.py", line 47, in Inventory
>> from ElasticIsotropic3D import ElasticIsotropic3D
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/ElasticIsotropic3D.py", line 19, in ?
>> from ElasticMaterial import ElasticMaterial
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/ElasticMaterial.py", line 20, in ?
>> from Material import Material
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/Material.py", line 30, in ?
>> class Material(Component):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/Material.py", line 43, in Material
>> class Inventory(Component.Inventory):
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/pylith/materials/Material.py", line 67, in Inventory
>> from spatialdata.spatialdb.SimpleDB import SimpleDB
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/spatialdata-0.3.0-py2.4.egg/spatialdata/spatialdb/
>> SimpleDB.py", line 19, in ?
>> from SpatialDB import SpatialDB
>> File "/home/dicaprio/local/pylith-build/lib/python2.4/site-
>> packages/spatialdata-0.3.0-py2.4.egg/spatialdata/spatialdb/
>> SpatialDB.py", line 21, in ?
>> import spatialdb as bindings
>> ImportError: No module named spatialdb
>> /home/dicaprio/local/pylith-build/bin/pylith: /home/dicaprio/local/
>> pylith-build/bin/nemesis: exit 1
>> ---------------------------------------------------------------------
>> ---------------------------------------------------------------------
>> ------------------------------ Thanks,
>> Chris
>> On Sep 26, 2007, at 12:36 PM, Brad Aagaard wrote:
>>> On Wednesday 26 September 2007, Christopher DiCaprio wrote:
>>>> I'm on a 32 bit machine. The only place where the pytests and
>>>> libtests directories are located are in the build directory
>>>> (everything is under a directory called pylith-build so it's a bit
>>>> misleading); is that an error?
>>>
>>> No. The tests are run from the build (they aren't part of the
>>> installation).
>>>
>>>> There is no geocoordsmodule.so file only libspatialdata.so
>>>
>>> You need to configure with --enable-pythia to build the modules.
>>> The default
>>> is to allow spatialdata to be used without Python.
>>>
>>> Brad
>> ---------------------------------------------------------------------
>> ---
>> _______________________________________________
>> CIG-SHORT mailing list
>> CIG-SHORT at geodynamics.org
>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>
More information about the CIG-SHORT
mailing list