Hi all,
the main issue with building a recent DOLFIN is that it uses by default
python 3 (I already built all dependencies with python 2). Luckily,
this can be disabled in your easyconfig with:
configopts += "-DDOLFIN_USE_PYTHON3=OFF "
However, the issue was that the swig files come pre-packaged for python 3
in the source directory.
Even though the configure procedure adds swig files for python 2 in the build
directory, it somehow picks up the swig files from the source directory during
the build. So I had to add the attached patch to also replace the swig files in
the source directory.
Another issue would pop up when building DOLFIN with an RPATH ('No module named
_common').
A fix for the build of DOLFIN with an RPATH was included in EasyBuild 3.5.1.
Cheers,
John
--
We are ISO 27001 certified and meet the high requirements for information
security.
| John Donners | Senior consultant | Compute | SURFsara | Science Park 140 |
1098 XG Amsterdam | Nederland |
T (31)6 19039023 | [email protected] | www.surfsara.nl |
Aanwezig op | ma | di | wo | do | vr
----- Original Message -----
From: "John Donners" <[email protected]>
To: "easybuild" <[email protected]>
Sent: Thursday, 1 February, 2018 07:13:30
Subject: Re: [easybuild] DOLFIN and Fenics
I could compile DOLFIN 2017.1 with intel 2016b. We can have a look today.
Verstuurd vanaf mijn iPhone
> Op 31 jan. 2018 om 22:51 heeft Lev Lafayette <[email protected]>
> het volgende geschreven:
>
>> On Wed, 2018-01-31 at 11:35 +0100, Julian Bigge wrote:
>> Hello fellow Easybuilders,
>>
>> we are currently working on an Easyconfig for the DOLFIN and Fenics
>> python
>> packages but are facing some linker errors when trying to build an
>> updated
>> Trilinos-12.12.1 with Python-2.7.14 in the foss/2017b toolchain. This
>> slows
>> down development of these easyconfigs a lot.
>>
>> So, maybe there are some users who got a relatively recent version of
>> DOLFIN
>> and Fenics (newer than the one in the easybuild-repo) up and running
>> and are
>> willing to share their solution?
>
> I would be interested in hearing about this as well; I managed to get
> that mountain of dependencies installed in Python-2.7.9 and 2.7.11
> installed but not DOLFIN itself.
>
> Have you applied the standard patches (e.g., petsc-slepc-libs.patch and
>
> SuiteSparse-4.3.patch)?
>
>
> --
> Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA
> (Tech Mngmnt) (Chifley)
> HPC Support and Training Officer +61383444193 +61432255208
> Department of Infrastructure Services, University of Melbourne--- dolfin/swig/CMakeLists.txt.orig 2017-05-09 17:01:18.000000000 +0200
+++ dolfin/swig/CMakeLists.txt 2017-12-21 22:28:22.762103283 +0100
@@ -49,6 +49,12 @@
execute_process(
COMMAND ${PYTHON_EXECUTABLE} ${DOLFIN_SOURCE_DIR}/cmake/scripts/generate-swig-docstrings.py ${CMAKE_BINARY_DIR}
WORKING_DIRECTORY ${DOLFIN_SOURCE_DIR})
+ execute_process(
+ COMMAND ${PYTHON_EXECUTABLE} ${DOLFIN_SOURCE_DIR}/cmake/scripts/generate-swig-interface.py ${CMAKE_SOURCE_DIR}
+ WORKING_DIRECTORY ${DOLFIN_SOURCE_DIR})
+ execute_process(
+ COMMAND ${PYTHON_EXECUTABLE} ${DOLFIN_SOURCE_DIR}/cmake/scripts/generate-swig-docstrings.py ${CMAKE_SOURCE_DIR}
+ WORKING_DIRECTORY ${DOLFIN_SOURCE_DIR})
endif()
# Get combined modules
