yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #05992
[Bug 666876] Re: unregistered class when built at maverick
** Attachment added: "script testing io of all yade classes"
https://bugs.launchpad.net/bugs/666876/+attachment/1712032/+files/save-class.py
** Changed in: yade
Importance: Undecided => High
** Changed in: yade
Status: New => Confirmed
** Changed in: yade
Milestone: None => 0.60
--
unregistered class when built at maverick
https://bugs.launchpad.net/bugs/666876
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
Status in Yet Another Dynamic Engine: Confirmed
Bug description:
The problems with "unregistered class" seem to re-surface at maverick. The packaged version (bzr2460) runs the attached script just fine, but manually-compiled versions fail:
This is what classes fail to save, a g++ build: ['FrictMat', 'PeriodicEngine', 'BodyCallback', 'GlIGeomFunctor', 'IntrCallback', 'Collider', 'BoundDispatcher', 'IGeomFunctor', 'ElastMat', 'LawFunctor', 'FrictPhys', 'ScGeom', 'TriaxialStressController', 'GlIPhysFunctor', 'BoundaryController', 'GenericSpheresContact', 'Dem3DofGeom', 'BoundFunctor']
This is with clang: ['PeriodicEngine', 'Recorder', 'BodyCallback', 'GlIGeomFunctor', 'FrictPhys', 'TriaxialStressController', 'GlIPhysFunctor', 'BoundaryController', 'GenericSpheresContact', 'KinemSimpleShearBox', 'Dem3DofGeom', 'Sphere']
Everything is fine with lucid.
I added these tests to the regression suite: starting from r2511, running --test will also say if some classes fail to be saved (and loaded).
References