yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #00064
Re: float, double, the DOUBLE_PRECISION flag
> FATAL
> /home/3S-LAB/bchareyre/Programmation/Yade-Sources/SVN-commitable/trunk/yade-core/src/yade/Omega.cpp:272
> scanPlugins: Undefined symbol
> `Math<float>::ZERO_TOLERANCE(/home/bchareyre/Programmation/YADE/lib/yade/yade-libs/libyade-lib-computational-geometry.so:
> undefined symbol: _ZN4MathIfE14ZERO_TOLERANCEE).
> Couldn't load everything, some stuff may work incorrectly.
There is a symbol that cannot be resolved. As a workaround, you can
delete the computation-geometry plugin which IIRC is not used. A quick
look into the .pro file reveals that it doesn't link with Wm3Foundation
where this symbol is defined:
$ nm --demangle /usr/local/lib/libWm3Foundation.a| grep ZERO_TOLERANCE
...
00000030 R Wm3::Math<double>::ZERO_TOLERANCE
00000004 R Wm3::Math<float>::ZERO_TOLERANCE
...
Try that, hope that works.
>> DEBUG
>> /home/3S-LAB/bchareyre/Programmation/Yade-Sources/SVN-commitable/trunk/yade-core/src/yade/Omega.cpp:238
>> scanPlugins: File not considered a plugin: libSphericalDEMSimulator.so.1.
I thought I disabled debugging messages by default
(yade-lib-base/Logging.hpp). Explanation: I restricted what files are
considered to be loaded only to those that satisfy the criterion that
libraryNameToSystemName(systemNameToLibraryName(filename))==filename,
which practically means only files "lib*.so". This one ends with .so.1,
hence is skipped. The reason for that was to be able to have other files
in plugin directories without getting errors.
Sorry for that.
Vaclav
_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev
Follow ups
References
-
float, double, the DOUBLE_PRECISION flag
From: Janek Kozicki, 2006-12-08
-
Re: float, double, the DOUBLE_PRECISION flag
From: Vaclav SMILAUER, 2006-12-11
-
Re: float, double, the DOUBLE_PRECISION flag
From: Bruno Chareyre, 2006-12-15
-
Re: float, double, the DOUBLE_PRECISION flag
From: Bruno Chareyre, 2006-12-15