Yade

compiled YADE ?!

Asked by Christian Jakob

Hi@all,

Since three days I tried to compile Yade with scons (bzr2811) on Mandriva
2010.2. This is the result:

START-------------------------------------------------------------------------------------------------------------------

[me@localhost yade]$ scons
scons: Reading SConscript files ...
@@@ Using profile default (scons.profile-default) @@@
Eigen 2 math library will be used
Yade version is `bzr2811' (bzr2811), installed files will be suffixed with `-
bzr2811'.
All intermediary files will be in `/home/me/install-data-external-
packages/build-bzr2811'.
Checking whether c++ compiler "g++" works...(cached) yes
Finding libstdc++ library... (cached) /usr/lib64/libstdc++.so.6
Checking for pthread_exit(NULL) in C library pthread... (cached) yes
Checking for Python development files... (cached) ok
Checking for C++ header file /usr/lib64/python2.6/site-
packages/numpy/core/include/numpy/ndarrayobject.h... (cached) yes
Checking for required python modules... (cached) all ok
Checking boost libraries... (cached) all ok
Checking for C++ header file boost/foreach.hpp... (cached) yes
Checking for C++ header file Eigen/Core... (cached) yes
Checking for C++ header file loki/NullType.h... (cached) yes
Checking for glutGetModifiers() in C++ library glut... (cached) yes
Checking for QGLViewer() in C++ library qglviewer-qt4... (cached) no
Checking for QGLViewer() in C++ library libQGLViewer... (cached) yes
Checking for vtkInstantiator::New() in C++ library vtkCommon... (cached) yes
scons: done reading SConscript files.
scons: Building targets ...
C /home/me/install-data-external-packages/build-bzr2811/core/core.cpp
C /home/me/install-data-external-packages/build-bzr2811/lib/yade-support.cpp
In file included from /usr/include/boost/python/object/function_handle.hpp:10,
                 from
/usr/include/boost/python/converter/arg_to_python.hpp:19,
                 from /usr/include/boost/python/call.hpp:15,
                 from /usr/include/boost/python/object_core.hpp:12,
                 from /usr/include/boost/python/args.hpp:25,
                 from /usr/include/boost/python.hpp:11,
                 from /home/me/install-data-external-
packages/yade/lib/serialization/Serializable.hpp:23,
                 from /home/me/install-data-external-
packages/yade/lib/serialization/Serializable.cpp:11,
                 from /home/me/install-data-external-packages/build-
bzr2811/lib/yade-support.cpp:5:
/home/me/install-data-external-
packages/yade/lib/serialization/Serializable.hpp: In member function
'PyObject* boost::python::objects::caller_py_function_impl<Caller>::operator()
(PyObject*, PyObject*) [with Caller = boost::python::detail::caller<PyObject*
(*)(Serializable&, const Serializable&), boost::python::default_call_policies,
boost::mpl::vector3<PyObject*, Serializable&, const Serializable&> >]':
/home/me/install-data-external-
packages/yade/lib/serialization/Serializable.hpp:262: warning: dereferencing
pointer 'p.2598' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/factory/Factorable.hpp:63: warning: dereferencing
pointer 'this.597' does break strict-aliasing rules
/home/me/install-data-external-
packages/yade/lib/serialization/Serializable.hpp:262: note: initialized from
here
/home/me/install-data-external-
packages/yade/lib/serialization/Serializable.hpp:262: warning: dereferencing
pointer 'p.2598' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/factory/Factorable.hpp:63: warning: dereferencing
pointer 'this.597' does break strict-aliasing rules
/home/me/install-data-external-
packages/yade/lib/serialization/Serializable.hpp:262: note: initialized from
here
C /home/me/install-data-external-packages/build-bzr2811/plugins12.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins13.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins14.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins15.cpp
In file included from /usr/include/boost/python/object/function_handle.hpp:10,
                 from
/usr/include/boost/python/converter/arg_to_python.hpp:19,
                 from /usr/include/boost/python/call.hpp:15,
                 from /usr/include/boost/python/object_core.hpp:12,
                 from /usr/include/boost/python/args.hpp:25,
                 from /usr/include/boost/python.hpp:11,
                 from /home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/serialization/Serializable.hpp:23,
                 from /home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/multimethods/FunctorWrapper.hpp:12,
                 from /home/me/install-data-external-packages/build-
bzr2811/include/yade/pkg/common/GLDrawFunctors.hpp:6,
                 from /home/me/install-data-external-packages/build-
bzr2811/include/yade/pkg/common/Gl1_Facet.hpp:11,
                 from /home/me/install-data-external-
packages/yade/pkg/common/Gl1_Facet.cpp:11,
                 from /home/me/install-data-external-packages/build-
bzr2811/plugins13.cpp:1:
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp: In member function 'PyObject*
boost::python::objects::caller_py_function_impl<Caller>::operator()(PyObject*,
PyObject*) [with Caller =
boost::python::detail::caller<boost::python::detail::member<OpenMPAccumulator<double>,
Law2_ScGeom_MindlinPhys_Mindlin>, boost::python::default_call_policies,
boost::mpl::vector3<void, Law2_ScGeom_MindlinPhys_Mindlin&, const
OpenMPAccumulator<double>&> >]':
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp:100: warning: dereferencing
pointer 'p.21891' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp:100: warning: dereferencing
pointer 'p.21891' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp: In member function 'PyObject*
boost::python::objects::caller_py_function_impl<Caller>::operator()(PyObject*,
PyObject*) [with Caller =
boost::python::detail::caller<boost::python::detail::member<OpenMPAccumulator<double>,
Law2_ScGeom_MindlinPhys_Mindlin>,
boost::python::return_value_policy<boost::python::return_by_value,
boost::python::default_call_policies>, boost::mpl::vector3<void,
Law2_ScGeom_MindlinPhys_Mindlin&, const OpenMPAccumulator<double>&> >]':
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp:100: warning: dereferencing
pointer 'p.21891' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp:100: warning: dereferencing
pointer 'p.21891' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp: In member function 'PyObject*
boost::python::objects::caller_py_function_impl<Caller>::operator()(PyObject*,
PyObject*) [with Caller = boost::python::detail::caller<void (*)
(Law2_ScGeom_MindlinPhys_Mindlin&, const OpenMPAccumulator<double>&),
boost::python::default_call_policies, boost::mpl::vector3<void,
Law2_ScGeom_MindlinPhys_Mindlin&, const OpenMPAccumulator<double>&> >]':
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp:100: warning: dereferencing
pointer 'p.21891' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
/home/me/install-data-external-packages/build-
bzr2811/include/yade/lib/base/openmp-accu.hpp:100: warning: dereferencing
pointer 'p.21891' does break strict-aliasing rules
/usr/include/boost/python/detail/destroy.hpp:90: note: initialized from here
C /home/me/install-data-external-packages/build-bzr2811/plugins0.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins1.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins2.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins3.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins4.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins5.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins6.cpp
In file included from /usr/lib/gcc/x86_64-manbo-linux-
gnu/4.4.3/../../../../include/c++/4.4.3/backward/strstream:46,
                 from /usr/include/vtk/vtkIOStream.h:112,
                 from /usr/include/vtk/vtkSystemIncludes.h:40,
                 from /usr/include/vtk/vtkIndent.h:24,
                 from /usr/include/vtk/vtkObjectBase.h:43,
                 from /usr/include/vtk/vtkObject.h:41,
                 from /usr/include/vtk/vtkCellArray.h:35,
                 from /home/me/install-data-external-
packages/yade/pkg/dem/VTKRecorder.cpp:7,
                 from /home/me/install-data-external-packages/build-
bzr2811/plugins6.cpp:2:
/usr/lib/gcc/x86_64-manbo-linux-
gnu/4.4.3/../../../../include/c++/4.4.3/backward/backward_warning.h:28:2:
warning: #warning This file includes at least one deprecated or antiquated
header which may be removed without further notice at a future date. Please
use a non-deprecated interface with equivalent functionality instead. For a
listing of replacement headers and interfaces, consult the file
backward_warning.h. To disable this warning use -Wno-deprecated.
C /home/me/install-data-external-packages/build-bzr2811/plugins7.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins8.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins9.cpp
In file included from /home/me/install-data-external-packages/build-
bzr2811/plugins9.cpp:7:
/home/me/install-data-external-packages/yade/pkg/dem/DomainLimiter.cpp: In
member function 'virtual void LawTester::action()':
/home/me/install-data-external-packages/yade/pkg/dem/DomainLimiter.cpp:218:
warning: comparison between signed and unsigned integer expressions
C /home/me/install-data-external-packages/build-bzr2811/plugins10.cpp
C /home/me/install-data-external-packages/build-bzr2811/plugins11.cpp
C py/mathWrap/miniEigen.cpp
L libplugins.so
C py/WeightedAverage2d.cpp
C py/wrapper/customConverters.cpp
> /home/me/YADE/lib/yade-bzr2811/plugins/libplugins.so
C py/_eudoxos.cpp
In file included from /usr/lib/gcc/x86_64-manbo-linux-
gnu/4.4.3/../../../../include/c++/4.4.3/backward/strstream:46,
                 from /usr/include/vtk/vtkIOStream.h:112,
                 from /usr/include/vtk/vtkSystemIncludes.h:40,
                 from /usr/include/vtk/vtkIndent.h:24,
                 from /usr/include/vtk/vtkObjectBase.h:43,
                 from /usr/include/vtk/vtkObject.h:41,
                 from /usr/include/vtk/vtkLocator.h:53,
                 from /usr/include/vtk/vtkAbstractPointLocator.h:27,
                 from /usr/include/vtk/vtkPointLocator.h:39,
                 from py/_eudoxos.cpp:13:
/usr/lib/gcc/x86_64-manbo-linux-
gnu/4.4.3/../../../../include/c++/4.4.3/backward/backward_warning.h:28:2:
warning: #warning This file includes at least one deprecated or antiquated
header which may be removed without further notice at a future date. Please
use a non-deprecated interface with equivalent functionality instead. For a
listing of replacement headers and interfaces, consult the file
backward_warning.h. To disable this warning use -Wno-deprecated.
L _customConverters.so
C py/pack/_packObb.cpp
C py/pack/_packPredicates.cpp
C py/pack/_packSpheres.cpp
L _eudoxos.so
C py/_utils.cpp
L _packSpheres.so
C core/main/pyboot.cpp
C py/log.cpp
C /home/me/install-data-external-packages/build-
bzr2811/gui/qt4/moc_OpenGLManager.cc
L _utils.so
C gui/qt4/GLViewer.cpp
C gui/qt4/_GLViewer.cpp
C gui/qt4/OpenGLManager.cpp
C /home/me/install-data-external-packages/build-
bzr2811/gui/qt4/moc_GLViewer.cc
C py/wrapper/yadeWrapper.cpp
L _GLViewer.so
L wrapper.so
scons: done building targets.

END-----------------------------------------------------------------------------------------------------------------

I have four questions:

1. How can I fix the problem with qt4 library?

Checking for QGLViewer() in C++ library qglviewer-qt4... (cached) no

... paths in scon.profile-default is correct:

PREFIX = '/home/me/YADE'
features = 'opengl,openmp,qt4,vtk'
CPPPATH =
'/usr/include/vtk-5.0:/usr/include/vtk-5.2:/usr/include/vtk-5.4:/usr/include/vtk-5.6:/usr/include/vtk:/usr/include/eigen2'
LIBPATH = '/usr/lib64:/usr/lib'
QT4DIR = '/usr/lib/qt4'
CXXFLAGS = []
SHCCFLAGS = ['-fPIC']

2. Is compilation completed correctly? There are several warnings (see
above)...

3. If compilation was ok, how can I start yade? There is no executable in
/home/me/YADE ... Do I have to install yade somehow?

[me@localhost bin]$ pwd
/home/me/YADE/bin
[me@localhost bin]$ ls -lah
insgesamt 56K
drwxr-xr-x 2 me me 4,0K 2011-04-14 12:01 ./
drwxr-xr-x 4 me me 4,0K 2011-04-14 12:01 ../
-rwxr-xr-x 1 me me 13K 2011-04-14 12:01 yade-bzr2811*
-rwxr-xr-x 1 me me 29K 2011-04-14 12:01 yade-bzr2811-batch*
[me@localhost bin]$

4. I did not use the feature 'log4cxx' because there is no package available
for my distribution. Will this lead to problems, when using yade (later)?

Regards,

Christian.

Question information

Language:
English Edit question
Status:
Solved
For:
Yade Edit question
Assignee:
No assignee Edit question
Solved by:
Christian Jakob
Solved:
Last query:
Last reply:
Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#1

OK, thank you,

new problem:

[me@localhost bin]$ ./yade-bzr2811
Welcome to Yade bzr2811
TCP python prompt on localhost:9000, auth cookie `ukcsyd'
XMLRPC info provider on http://localhost:21000
segmentation fault
[me@localhost bin]$

message from Jerome------------------------------------------

Hello,

Better ask your question on https://answers.launchpad.net/yade. Nevertheless

- your compilation ended correctly, see : "scons: done building
targets. " Warnings are "just" warnings, not compilation failure

- about qt4, I guess you will have no problem since
"Checking for QGLViewer() in C++ library libQGLViewer... (cached) yes "
even if "Checking for QGLViewer() in C++ library qglviewer-qt4...
(cached) no "
and then QGLViewer() was finally found

- to launch Yade, type (you are in the good directory)
"./yade-bzr2811" (or with the * if it is here). Just as for any linux
executable

- log4cxx is for logging (see on the Yade manual on internet), not mandatory

Jerome

Revision history for this message
Anton Gladky (gladky-anton) said : 		#2

Hi,

> 1. How can I fix the problem with qt4 library?

You don't have problems with this library. It is found, but for
RPM-based distributions it has another name:
> Checking for QGLViewer() in C++ library qglviewer-qt4... (cached) no
> Checking for QGLViewer() in C++ library libQGLViewer... (cached) yes

> 2. Is compilation completed correctly? There are several warnings (see
> above)...
> 3. If compilation was ok, how can I start yade? There is no executable in
> /home/me/YADE ... Do I have to install yade somehow?

Compilation is ok, warnings are not a problem.
just run:
/home/me/YADE/bin/yade-bzr2811

> 4. I did not use the feature 'log4cxx' because there is no package available
> for my distribution. Will this lead to problems, when using yade (later)?

It is not a problem for the moment. You can try to install from
another RPM, should work.

Anton.

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#3

OK, thank you,

new problem:

[me@localhost bin]$ ./yade-bzr2811
Welcome to Yade bzr2811
TCP python prompt on localhost:9000, auth cookie `ukcsyd'
XMLRPC info provider on http://localhost:21000
segmentation fault
[me@localhost bin]$

Revision history for this message
Anton Gladky (gladky-anton) said : 		#4

It is odd.
You can recompile yade in debug mode (add "Debug=True" to scons.profile-default) and then start the programm again.
The complete output of the crash can be useful.
But I am afraid, there are almost no users of Mandriva here and it will be difficult to fix that.

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#5

Ok, I recompiled it with Debug = 1

result is the same error (see above)

I think nothing has changed, because Debug = 1 is default...

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#6

How can I find out what the source of the problem is?
Is there a log-file or something like that?

Revision history for this message
Anton Gladky (gladky-anton) said : 		#7

./yade-bzr2811 --debug

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#8

[me@localhost yade]$ yade --debug
Welcome to Yade bzr2811 (debug build)
TCP python prompt on localhost:9000, auth cookie `auckse'
XMLRPC info provider on http://localhost:21000
SIGSEGV/SIGABRT handler called; gdb batch file is `/tmp/yade-ZQPFNy/tmp-0'
GNU gdb (GDB) 7.1-1mdv2010.1 (Mandriva Linux release 2010.1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-mandriva-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
[Thread debugging using libthread_db enabled]
[New Thread 0x7f67a4a90710 (LWP 32010)]
[New Thread 0x7f67a5291710 (LWP 32009)]
0x00007f67c321eadd in waitpid () from /lib64/libc.so.6
No symbol "info" in current context.

Thread 3 (Thread 0x7f67a5291710 (LWP 32009)):
#0 0x00007f67c2d6b370 in sem_wait () from /lib64/libpthread.so.0
#1 0x00007f67c35e8468 in PyThread_acquire_lock () from /usr/lib64/libpython2.6.so.1.0
#2 0x00007f67c35c26f4 in PyEval_RestoreThread () from /usr/lib64/libpython2.6.so.1.0
#3 0x00007f67ab12d3af in ?? () from /usr/lib64/python2.6/lib-dynload/select.so
#4 0x00007f67c35c0707 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0
#5 0x00007f67c35c25c0 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0
#6 0x00007f67c35c082b in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0
#7 0x00007f67c35c25c0 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0
#8 0x00007f67c35554af in ?? () from /usr/lib64/libpython2.6.so.1.0
#9 0x00007f67c352e103 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#10 0x00007f67c3540d0f in ?? () from /usr/lib64/libpython2.6.so.1.0
#11 0x00007f67c352e103 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#12 0x00007f67c35bac13 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.6.so.1.0
#13 0x00007f67a529a6db in ?? () from /usr/lib64/python2.6/site-packages/sip.so
#14 0x00007f67a552f577 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so
#15 0x00007f67a555fed9 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so
#16 0x00007f67be02e715 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007f67c2d64a5d in start_thread () from /lib64/libpthread.so.0
#18 0x00007f67c325915d in clone () from /lib64/libc.so.6
#19 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f67a4a90710 (LWP 32010)):
#0 0x00007f67c2d6b370 in sem_wait () from /lib64/libpthread.so.0
#1 0x00007f67c35e8468 in PyThread_acquire_lock () from /usr/lib64/libpython2.6.so.1.0
#2 0x00007f67c35c26f4 in PyEval_RestoreThread () from /usr/lib64/libpython2.6.so.1.0
#3 0x00007f67ab12d3af in ?? () from /usr/lib64/python2.6/lib-dynload/select.so
#4 0x00007f67c35c0707 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0
#5 0x00007f67c35c25c0 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0
#6 0x00007f67c35c082b in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0
#7 0x00007f67c35c25c0 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0
#8 0x00007f67c35554af in ?? () from /usr/lib64/libpython2.6.so.1.0
#9 0x00007f67c352e103 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#10 0x00007f67c3540d0f in ?? () from /usr/lib64/libpython2.6.so.1.0
#11 0x00007f67c352e103 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#12 0x00007f67c35bac13 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.6.so.1.0
#13 0x00007f67a529a6db in ?? () from /usr/lib64/python2.6/site-packages/sip.so
#14 0x00007f67a552f577 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so
#15 0x00007f67a555fed9 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so
#16 0x00007f67be02e715 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007f67c2d64a5d in start_thread () from /lib64/libpthread.so.0
#18 0x00007f67c325915d in clone () from /lib64/libc.so.6
#19 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f67c3a84700 (LWP 32005)):
#0 0x00007f67c321eadd in waitpid () from /lib64/libc.so.6
#1 0x00007f67c31ba861 in do_system () from /lib64/libc.so.6
#2 0x00007f67c31babc0 in system () from /lib64/libc.so.6
#3 0x00007f67c0cb6b70 in crashHandler (sig=11) at core/main/pyboot.cpp:45
#4 <signal handler called>
#5 0x00007f67bf5eedeb in glutInit () from /usr/lib64/libglut.so.3
#6 0x00007f67b10dd897 in OpenGLRenderer::init (this=0x2154600) at /home/me/install-data-external-packages/yade/pkg/common/OpenGLRenderer.cpp:48
#7 0x00007f67a36c0e16 in OpenGLManager::OpenGLManager (this=0x212eec0, parent=0x0) at gui/qt4/OpenGLManager.cpp:11
#8 0x00007f67a36a6181 in init_module__GLViewer () at gui/qt4/_GLViewer.cpp:91
#9 0x00007f67bf85031b in boost::python::handle_exception_impl(boost::function0<void>) () from /usr/lib64/libboost_python.so.1.42.0
#10 0x00007f67bf851023 in boost::python::detail::init_module(char const*, void (*)()) () from /usr/lib64/libboost_python.so.1.42.0
#11 0x00007f67a36a6120 in init_GLViewer () at gui/qt4/_GLViewer.cpp:88
#12 0x00007f67c35d5728 in _PyImport_LoadDynamicModule () from /usr/lib64/libpython2.6.so.1.0
#13 0x00007f67c35d3765 in ?? () from /usr/lib64/libpython2.6.so.1.0
#14 0x00007f67c35d39f4 in ?? () from /usr/lib64/libpython2.6.so.1.0
#15 0x00007f67c35d409e in ?? () from /usr/lib64/libpython2.6.so.1.0
#16 0x00007f67c35d4dd4 in PyImport_ImportModuleLevel () from /usr/lib64/libpython2.6.so.1.0
#17 0x00007f67c35ba6bf in ?? () from /usr/lib64/libpython2.6.so.1.0
#18 0x00007f67c352e103 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#19 0x00007f67c35bac13 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.6.so.1.0
#20 0x00007f67c35bd4ce in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0
#21 0x00007f67c35c25c0 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0
#22 0x00007f67c35c2692 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#23 0x00007f67c35d1d82 in PyImport_ExecCodeModuleEx () from /usr/lib64/libpython2.6.so.1.0
#24 0x00007f67c35d2276 in ?? () from /usr/lib64/libpython2.6.so.1.0
#25 0x00007f67c35d304f in ?? () from /usr/lib64/libpython2.6.so.1.0
#26 0x00007f67c35d3765 in ?? () from /usr/lib64/libpython2.6.so.1.0
#27 0x00007f67c35d39f4 in ?? () from /usr/lib64/libpython2.6.so.1.0
#28 0x00007f67c35d409e in ?? () from /usr/lib64/libpython2.6.so.1.0
#29 0x00007f67c35d4dd4 in PyImport_ImportModuleLevel () from /usr/lib64/libpython2.6.so.1.0
#30 0x00007f67c35ba6bf in ?? () from /usr/lib64/libpython2.6.so.1.0
#31 0x00007f67c352e103 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0
#32 0x00007f67c35bac13 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.6.so.1.0
#33 0x00007f67c35bd4ce in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0
#34 0x00007f67c35c25c0 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0
#35 0x00007f67c35c2692 in PyEval_EvalCode () from /usr/lib64/libpython2.6.so.1.0
#36 0x00007f67c35dcb5c in ?? () from /usr/lib64/libpython2.6.so.1.0
#37 0x00007f67c35dcc30 in PyRun_FileExFlags () from /usr/lib64/libpython2.6.so.1.0
#38 0x00007f67c35de10c in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.6.so.1.0
#39 0x00007f67c35ea751 in Py_Main () from /usr/lib64/libpython2.6.so.1.0
#40 0x00007f67c319cafd in __libc_start_main () from /lib64/libc.so.6
#41 0x0000000000400689 in _start ()
Speicherzugriffsfehler
[me@localhost yade]$

Revision history for this message
Anton Gladky (gladky-anton) said : 		#9

Difficult to say, why it crashes. It seems, that the crash comes from
glutInit function, which does not belong to yade.

If you want, you can try to compile without qt4 support.

./yade --debug --test

and

./yade --debug --check

just to verify, whether it works or not.

But I would suggest you to consider using something Debian-based or
Fedora-Suse at least, they should also work. As I know most of
yade-users are using Ubuntu.

Anton

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#10

Ok, Anton gave me the hint, that the problem has something to do with my VMware.
My host system is Windows XP and I created a virtual machine with VMware player 3.1.4.
Maybe there is a problem with graphics and the glutInit function, as you assumed.
I will compile without qt4 support and post the results in the next message.

[me@localhost ~]$ yade --debug --test
Math: Matrix3 operations ... ok
Math: Quaternion operations ... ok
Math: Vector2 operations ... ok
Math: Vector3 operations ... ok
Core: correct types are instantiated ... ok
Core: dispatcher ctors with functors ... ok
Core: Attr::hidden ... ok
Core: InteractionLoop special ctor ... ok
Core: invalid attribute access raises AttributeError ... ok
Core: Attr::noSave ... ok
Core: ParallelEngine special ctor ... ok
Core: class ctor's attributes ... ok
Core: Attr::triggerPostLoad ... ok
Core: dispatcher and functor type mismatch is detected ... ok
Bodies: erased bodies are None in python ... ok
Bodies: Iterator silently skips erased ones ... ok
Bodies: Iteration ... ok
Bodies: len(O.bodies) ... ok
Bodies: Negative index counts backwards (like python sequences). ... ok
I/O: All classes can be saved and loaded with boost::serialization ... WARNING: cannot open files used for capillary law, all forces will be null. Instructions on how to download and install them is found here : https://yade-dem.org/wiki/CapillaryTriaxialTest.
ok
Loop: dead engines are not run ... ok
Loop: O.engines can be modified inside the loop transparently. ... ok
Loop: substepping ... ok
Material+State: CpmMat returns CpmState when asked for newAssocState ... ok
Material+State: throws when body has material and state that don't work together. ... ok
Material+State: throws when body has material but NULL state. ... ok
Material: find by index or label; KeyError raised for invalid label. ... ok
Material: iteration over O.materials ... ok
Material: len(O.materials) ... ok
Material: negative index counts backwards. ... ok
Material: shared_ptr's makes change in material immediate everywhere ... ok
Material: shared_ptr's are preserved when saving/loading ... ok
PBC: degenerate cell raises exception ... ok
PBC: homothetic cell deformation adjusts particle position (homoDeform==1) ... ok
PBC: homothetic cell deformation adjusts particle velocity (homoDeform==3) ... ok
PBC: utils.kineticEnergy considers only fluctuation velocity, not the velocity gradient (homoDeform==3) ... ok
PBC: utils.kineticEnergy considers only fluctuation velocity, not the velocity gradient (homoDeform==1) ... ok
PBC: L3Geom computes incident velocity correctly (homoDeform==3) ... ok
PBC: L3Geom computes incident velocity correctly (homoDeform==1) ... ok
PBC: ScGeom computes incident velocity correctly (homoDeform==3) ... ok
PBC: ScGeom computes incident velocity correctly (homoDeform==1) ... ok
PBC: setBox modifies hSize correctly ... ok
PBC: chaing trsf changes hSize0, but does not modify hSize ... ok
PBC: velGrad changes hSize but not hSize0, accumulates in trsf ... ok
Clump: ids and flags consistency ... ok
Clump: mass, centroid, intertia ... ok
Clump: velocities of member assigned by NewtonIntegrator ... ok
CohesiveChain: velocity/positions tested in transient dynamics and equilibrium state ... ok
Doctest: yade.eudoxos.IntrSmooth3d ... ok
Doctest: yade.pack.SpherePack_toSimulation ... ok
Doctest: yade.plot.addAutoData ... ok
Doctest: yade.plot.addData ... ok
Doctest: yade.plot.plot ... ok
Doctest: yade.plot.saveDataTxt ... ok
Doctest: yade.utils.SpherePWaveTimeStep ... ok
Doctest: yade.utils.saveVars ... /home/me/YADE/lib/yade-bzr2811/dbg/py/yade/utils.py:55: UserWarning: Overwriting yade.params.something which already exists.
  if mark in yade.params.__dict__: warnings.warn('Overwriting yade.params.%s which already exists.'%mark)
ok
Doctest: yade.utils.sphere ... ok
Doctest: yade.utils.typedEngine ... ok

----------------------------------------------------------------------
Ran 58 tests in 8.772s

OK
*** ALL TESTS PASSED ***

[me@localhost ~]$ yade --debug --check
Welcome to Yade bzr2811 (debug build)
###################################
running: checkTestTriax.py
WARN py/log.cpp:49 logSetLevel: Yade was compiled without log4cxx support. Setting log levels from python will have no effect (warn once).
Status: success
___________________________________
###################################
running: checkWeight.py
Precalculated weight 4536.560323
Obtained weight 4536.560323
Status: success
___________________________________
###################################
running: checkTestDummy.py
checkTest mechanism
Status: success
___________________________________

[me@localhost ~]$ yade
Welcome to Yade bzr2811
TCP python prompt on localhost:9000, auth cookie `kudyse'
XMLRPC info provider on http://localhost:21000
Segmentation fault
[me@localhost ~]$

Revision history for this message
Anton Gladky (gladky-anton) said : 		#11

I am almost completely sure, that the problem is in VMware.
I heard, that there were some problems with 3D-support, that is why,
perhaps, yade crashes.

You can try VirtualBox, It has better 3D-support .

Anton

On Fri, Apr 15, 2011 at 9:17 AM, Christian Jakob
<email address hidden> wrote:
> Question #152794 on Yade changed:
> https://answers.launchpad.net/yade/+question/152794
>
> Christian Jakob posted a new comment:
> Ok, Anton gave me the hint, that the problem has something to do with my VMware.
> My host system is Windows XP and I created a virtual machine with VMware player 3.1.4.
> Maybe there is a problem with graphics and the glutInit function, as you assumed.
> I will compile without qt4 support and post the results in the next message.
>
> [me@localhost ~]$ yade --debug --test
> Math: Matrix3 operations ... ok
> Math: Quaternion operations ... ok
> Math: Vector2 operations ... ok
> Math: Vector3 operations ... ok
> Core: correct types are instantiated ... ok
> Core: dispatcher ctors with functors ... ok
> Core: Attr::hidden ... ok
> Core: InteractionLoop special ctor ... ok
> Core: invalid attribute access raises AttributeError ... ok
> Core: Attr::noSave ... ok
> Core: ParallelEngine special ctor ... ok
> Core: class ctor's attributes ... ok
> Core: Attr::triggerPostLoad ... ok
> Core: dispatcher and functor type mismatch is detected ... ok
> Bodies: erased bodies are None in python ... ok
> Bodies: Iterator silently skips erased ones ... ok
> Bodies: Iteration ... ok
> Bodies: len(O.bodies) ... ok
> Bodies: Negative index counts backwards (like python sequences). ... ok
> I/O: All classes can be saved and loaded with boost::serialization ... WARNING: cannot open files used for capillary law, all forces will be null. Instructions on how to download and install them is found here : https://yade-dem.org/wiki/CapillaryTriaxialTest.
> ok
> Loop: dead engines are not run ... ok
> Loop: O.engines can be modified inside the loop transparently. ... ok
> Loop: substepping ... ok
> Material+State: CpmMat returns CpmState when asked for newAssocState ... ok
> Material+State: throws when body has material and state that don't work together. ... ok
> Material+State: throws when body has material but NULL state. ... ok
> Material: find by index or label; KeyError raised for invalid label. ... ok
> Material: iteration over O.materials ... ok
> Material: len(O.materials) ... ok
> Material: negative index counts backwards. ... ok
> Material: shared_ptr's makes change in material immediate everywhere ... ok
> Material: shared_ptr's are preserved when saving/loading ... ok
> PBC: degenerate cell raises exception ... ok
> PBC: homothetic cell deformation adjusts particle position (homoDeform==1) ... ok
> PBC: homothetic cell deformation adjusts particle velocity (homoDeform==3) ... ok
> PBC: utils.kineticEnergy considers only fluctuation velocity, not the velocity gradient (homoDeform==3) ... ok
> PBC: utils.kineticEnergy considers only fluctuation velocity, not the velocity gradient (homoDeform==1) ... ok
> PBC: L3Geom computes incident velocity correctly (homoDeform==3) ... ok
> PBC: L3Geom computes incident velocity correctly (homoDeform==1) ... ok
> PBC: ScGeom computes incident velocity correctly (homoDeform==3) ... ok
> PBC: ScGeom computes incident velocity correctly (homoDeform==1) ... ok
> PBC: setBox modifies hSize correctly ... ok
> PBC: chaing trsf changes hSize0, but does not modify hSize ... ok
> PBC: velGrad changes hSize but not hSize0, accumulates in trsf ... ok
> Clump: ids and flags consistency ... ok
> Clump: mass, centroid, intertia ... ok
> Clump: velocities of member assigned by NewtonIntegrator ... ok
> CohesiveChain: velocity/positions tested in transient dynamics and equilibrium state ... ok
> Doctest: yade.eudoxos.IntrSmooth3d ... ok
> Doctest: yade.pack.SpherePack_toSimulation ... ok
> Doctest: yade.plot.addAutoData ... ok
> Doctest: yade.plot.addData ... ok
> Doctest: yade.plot.plot ... ok
> Doctest: yade.plot.saveDataTxt ... ok
> Doctest: yade.utils.SpherePWaveTimeStep ... ok
> Doctest: yade.utils.saveVars ... /home/me/YADE/lib/yade-bzr2811/dbg/py/yade/utils.py:55: UserWarning: Overwriting yade.params.something which already exists.
>  if mark in yade.params.__dict__: warnings.warn('Overwriting yade.params.%s which already exists.'%mark)
> ok
> Doctest: yade.utils.sphere ... ok
> Doctest: yade.utils.typedEngine ... ok
>
> ----------------------------------------------------------------------
> Ran 58 tests in 8.772s
>
> OK
> *** ALL TESTS PASSED ***
>
>
> [me@localhost ~]$ yade --debug --check
> Welcome to Yade bzr2811 (debug build)
> ###################################
> running:  checkTestTriax.py
> WARN  py/log.cpp:49 logSetLevel: Yade was compiled without log4cxx support. Setting log levels from python will have no effect (warn once).
> Status: success
> ___________________________________
> ###################################
> running:  checkWeight.py
> Precalculated weight 4536.560323
> Obtained weight 4536.560323
> Status: success
> ___________________________________
> ###################################
> running:  checkTestDummy.py
> checkTest mechanism
> Status: success
> ___________________________________
>
>
> [me@localhost ~]$ yade
> Welcome to Yade bzr2811
> TCP python prompt on localhost:9000, auth cookie `kudyse'
> XMLRPC info provider on http://localhost:21000
> Segmentation fault
> [me@localhost ~]$
>
> --
> You received this question notification because you are a member of
> yade-users, which is an answer contact for Yade.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users
> Post to     : <email address hidden>
> Unsubscribe : https://launchpad.net/~yade-users
> More help   : https://help.launchpad.net/ListHelp
>

Revision history for this message
Christian Jakob (jakob-ifgt) said : 		#12

[me@localhost yade]$ yade
Welcome to Yade bzr2811
TCP python prompt on localhost:9000, auth cookie `cusske'
XMLRPC info provider on http://localhost:21000
**********************************************************************
Welcome to IPython. I will try to create a personal configuration directory
where you can customize many aspects of IPython's functionality in:

/home/me/.ipython
Initializing from configuration: /usr/lib/python2.6/site-packages/IPython/UserConfig

Successful installation!

Please read the sections 'Initial Configuration' and 'Quick Tips' in the
IPython manual (there are both HTML and PDF versions supplied with the
distribution) to make sure that your system environment is properly configured
to take advantage of IPython's features.

Important note: the configuration system has changed! The old system is
still in place, but its setting may be partly overridden by the settings in
"~/.ipython/ipy_user_conf.py" config file. Please take a look at the file
if some of the new settings bother you.

Please press <RETURN> to start IPython.
**********************************************************************
[[ ^L clears screen, ^U kills line. F8 plot. ]]
Yade [1]:

Revision history for this message
Yade Guide (yade-guide) said : 		#13

Hi there! As an automated assistant, I've searched through some relevant threads and compiled a summary for your reference. Feel free to explore further by clicking on the links provided.

Title: "Problems with scons PREFIX=/home/daniela/YADE"
User successfully compiled Yade, resolved dependency cycle issues, and started it using 'yade-daily'. Despite this, they still encounter an ImportError. The user found success in running the simulation parallel using 'yade-bzr2880 --debug' suggested by Anton. The user is now deciding between 'yade-bzr2880' or 'yade-daily' for their simulation.
https://answers.launchpad.net/yade/+question/163713

Title: "compilation failed on debian wheezy"
The user encounters 'build-unknown' issue while compiling YADE with the latest git version (7b3752a) on Wheezy. The issue is expected to be resolved when python-git 0.3.2~RC1-1 migrates to Wheezy, and the user needs to clean their scons.profile.
https://answers.launchpad.net/yade/+question/193815

Title: "Compiling"
Elaheh encounters a 'SConstruct file not found' error while trying to compile 'trunk-2016.06a' from 'yade-source-1' folder, and seeks advice on resolving the issue and confirming if they have the latest version of YADE. Seti suggests using CMake for configuration and building or using packages instead of modifying the source code.
https://answers.launchpad.net/yade/+question/402288