Closed endJunction closed 5 years ago
Hi @endJunction,
Thank you for your interest in MGIS
and your feed-back.
MGIS
is a very young project, so it is not surprising that you face such issues when mixing versions/branches of TFEL
and MGIS
.
If you look at the front page of the project on github, you'll see:
- the master branch follows the evolution of the master branch of the TFEL project
- the rliv-1.0 follows the evolution of the 3.2.x series of the TFEL project. Note that this branch is not compatible with TFEL-3.2.0.
This is mostly du to the fact that I forgot to add support for stored and dissipated energies in the generic interface of MFront and that some of my early users urges me to correct that. As a consequence, the data structure passed the behaviour changed (two additional members), hence the segfault.
If you want to keep up with:
TFEL
3.2.0, then use release 1.0 of MGIS
rliv-3.2
branch of TFEL
, then use the rliv-1.0
branch of MGIS
master
branch of TFEL
, then use the master
branch of MGIS
Note that the master
branch is likely to evolve rapidly in the following week as we will start working on generalised and/or multiphysics behaviours in MFront.
As the project matures, things will stabilize, for the moment users will have to be a very cautious.
Do not hesitate if you have other feed-backs, features request, and so on.
Regards,
Thomas
Hi, I was trying to execute the tests from the current master (9b67ad18), but for all of the
IntegrateTest*
I get a SEGV.tfel version 3.2.0, which I got from the sourceforge site, gcc-8.2.1 on ArchLinux. steps to reproduce:
cmake runs fine, but complains about tfel's unknown option
--python-version
, saying afterwards that there areno tfel python bindings
.make check
compiles w/o interesting warnings, finally outputting:Running
tests/IntegrateTest tests/libBehaviourTest.so
in gdb yields following backtrace:Don't hesitate to ask for more output or testing -- maybe it's machine/OS specific.