Problem with libple.so.2

[Yvan Fournier]

Hello,

Checking the posts above, I remark that you should use either:

Code: Select all

CC=mpicc CXX=mpicxx

or:

Code: Select all

--with-mpi=/usr/lib/x86_64-linux-gnu/openmpi

but not both.

Also, as libtool was removed from PLE in code_saturne 7.2 but from the code itself only in 7.3, there might be related issues here.

In any case, code_saturne versions 7.2 and 7.3 will be retired next month when v8.0 is released, and the v8.0 validation is well underway, so it should already be more stable than those intermediate versions. So upgrading to v8.0-beta (i.e. the v8.0 git branch) is probably a good idea.

Best regards,

Yvan

[jcharris]

Are there any connections between the EDF team and the group (Debian Science Team) that put code_saturne in their package managers ?

https://packages.debian.org/search?keyw ... de-saturne
https://packages.ubuntu.com/search?keyw ... de-saturne

If so, it could be useful, especially for more casual use, to update from v6.

[Yvan Fournier]

Hello,

There are occasional contacts. It is possible to send messages to the packager through this page https://packages.debian.org/sid/code-saturne.

Usually, the version was updated, but for some reason, v7.0 was not. I do not know why, as I am sure the packager is aware of the v7.0 release. Anyways, the release dates for stable code_saturne and Debian release version was always off, so the version under Debian was often an unstable version.

And downstream of Debian, Ubuntu packages are almost unusable (user-defined functions not working).

So I have (almost) given up on packaging...

Best regards,

Yvan