Re: problem with "pkg -forge fem-fenics"

[Arnaud Lejeune]

Le 27/03/2017 17:33, Arnaud Lejeune a écrit :

Le 27/03/2017 17:20, Nicholas Jankowski a écrit :

On Mon, Mar 27, 2017 at 11:18 AM, Arnaud Lejeune <address@hidden> wrote:

Yes

Le 27/03/2017 16:54, Nicholas Jankowski a écrit :

On Mon, Mar 27, 2017 at 5:25 AM, arnaudl <address@hidden> wrote:

Hello,

I am working on:
-> Linux version 4.4.0-67-generic (address@hidden) (gcc version 5.4.0
20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) )
-> Octave version 4.0.0

Trying to install fem-fenics using
 "pkg -forge fem-fenics"

first question, did you mean:

pkg install -forge fem-fenics

?

Yes I mean
pkg install -forge fem-fenics

Downloading fem-fenics sources and looking at Mesh.cc, perhaps could it be a problem with "size_t" as "_msh" seems to be a dolfin::mesh shared_ptr ?

Dolfin version is the stable one installed with "apt-get".

Note that during the fem-fenis installation, compilation of fem-fenics sources uses the following CPPFLAGS options:
-DDOLFIN_VERSION=\"2016.2.0" -DDOLFIN_SIZE_T=8 -DDOLFIN_LA_INDEX_SIZE=4

Thanks for your help.

please keep the help list on the replies, as I'm not familiar enough with this package to help further myself.

Ok,

looking at the source file "MeshTopology.h" from Dolfin package, one could see that  :

_msh->topology ().global_indices(std::size_t d) 

returns a 

const std::vector< std::int64_t > &

The compilation seems to fail as std::int64_t is not equivalent to std::size_t.

Is there a way to change fem-fenics options to solve this problem ?

Thanks

Trying to find a solution, I found a change between dolfin version 1.3.0 (required for last fem-fenics package ) and the stable one  installed with apt-get (2016.2.0).
MeshTopology.h :
--> dolfin version 1.3.0 untl version 2016.1.0

const std::vector< std::size_t > & global_indices(std::size_t d) const

--> dolfin version 2016.2.0

const std::vector< std::int64_t > & global_indices(std::size_t d) const
***************************************************************************

Then I think it's really a bug and one has to change Mesh.cc in the fem-fenics sources.

So I go back to 2016.1.0


Arnaud