Re: [Yade-users] [Question #294790]: YADE-1.20.0 compiled with Intel Compiler

[Anton Gladky]

Question #294790 on Yade changed:
https://answers.launchpad.net/yade/+question/294790

Status: Open => Answered

Anton Gladky proposed the following answer:
The purpose of compiling with gcc is just to check,
whether gcc is able to produce the working binaries
for your platform.

You can theoretically write a simple C++ code, link it
against libyade and use this C++ program without
python bindings. But it can also be not so easy
and bug-free though

Cheers

Anton

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp

Re: [Yade-users] [Question #294790]: YADE-1.20.0 compiled with Intel Compiler

[Feng Chen]

Question #294790 on Yade changed:
https://answers.launchpad.net/yade/+question/294790

Status: Answered => Open

Feng Chen is still having a problem:
Hi, Anton:

The purpose of using the intel compiler is that I intended to use the
Xeon Phi co-processor which might be able to have some speedup on openmp
(shared memory model) enabled codes (which I think YADE should be a good
candidate), in order to use it the first step is to compile with the
intel's compiler. Currently gcc does not have  support for Knights
Corner vector instructions therefore should not be used.

Is it possible to compile part of yade and run some benchmark problems
(which was true many years ago^_^) without the python interface (the
benchmark/optimization using Xeon Phi will not need python)?

Thanks

Feng

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp

Re: [Yade-users] [Question #294790]: YADE-1.20.0 compiled with Intel Compiler

[Anton Gladky]

Question #294790 on Yade changed:
https://answers.launchpad.net/yade/+question/294790

Status: Open => Answered

Anton Gladky proposed the following answer:
Difficult to say. Looks like a problem in Boost. Try to use
another boost-version. Can you try to compile with gcc?

Anton


2016-06-02 22:17 GMT+02:00 Feng Chen :
> Question #294790 on Yade changed:
> https://answers.launchpad.net/yade/+question/294790
>
> Status: Answered => Open
>
> Feng Chen is still having a problem:
> Hi, Anton, thanks for your quick reply, I attached here the debug info
> for the run, it seems quite long, do you have any idea which part went
> wrong?
>
> [fchen14@host003 bin]$ ./yade-1.20.0 >err.log 2>&1
> Segmentation fault

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp

Re: [Yade-users] [Question #294790]: YADE-1.20.0 compiled with Intel Compiler

[Feng Chen]

Question #294790 on Yade changed:
https://answers.launchpad.net/yade/+question/294790

Status: Answered => Open

Feng Chen is still having a problem:
Hi, Anton, thanks for your quick reply, I attached here the debug info
for the run, it seems quite long, do you have any idea which part went
wrong?

[fchen14@host003 bin]$ ./yade-1.20.0 >err.log 2>&1
Segmentation fault

below is the err.log:
---
Welcome to Yade 1.20.0 
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.hpp:108 Omega: Constructing 
Omega.
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:212 loadPlugins: 
Loading plugin /project/fchen14/yade/install/lib64/yade-1.20.0/libyade.so
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:136 
buildDynlibDatabase: called with 234 plugins.
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin AxialGravityEngine
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BicyclePedalEngine
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_Box_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_ChainedCylinder_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_Cylinder_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_Facet_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_GridConnection_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_Sphere_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_Tetra_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bo1_Wall_Aabb
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Body
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Bound
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BoundDispatcher
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BoundFunctor
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BoundaryController
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Box
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BoxFactory
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BubbleMat
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin BubblePhys
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CapillaryPhys
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CapillaryStressRecorder
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CapillaryTriaxialTest
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Cell
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CentralGravityEngine
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin ChCylGeom6D
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin ChainedCylinder
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin ChainedState
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CircularFactory
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Clump
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CohFrictMat
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CohFrictPhys
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CohesiveFrictionalContactLaw
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CohesiveTriaxialTest
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin Collider
DEBUG /project/fchen14/yade/trunk-1.20.0/core/Omega.cpp:142 
buildDynlibDatabase: Factoring plugin CombinedKinematicEngine
DEBUG 

Re: [Yade-users] [Question #294790]: YADE-1.20.0 compiled with Intel Compiler

[Anton Gladky]

Question #294790 on Yade changed:
https://answers.launchpad.net/yade/+question/294790

Status: Open => Answered

Anton Gladky proposed the following answer:
Hi,

you need to compile Yade in debug-mode to get debugging symbols:
-DDEBUG=1 option on the cmake-step.

After that you start Yade and should get a lot of information during 
the crash, which can be useful to understand the source the problems. 

Regards

Anton

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp