Morten Piibeleht

Alright, so it is that the compiler has become more strict. It should be sufficient then to pass the [appropriate `CMAKE_Fortran_FLAGS`](https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_FLAGS.html) to CMake. For that you need to bypass `configure.sh`...

Good catch @jagot! @hf6391964 Have you had any luck with the proposed CMake workaround? If it looks like it is working, I would go ahead and close this in favour...

> I had 'name' in angular brackets and they did not display. Markdown [supports (limited) HTML](https://daringfireball.net/projects/markdown/syntax#html), so it most likely interpreted `` as an HTML tag. Surrounding it with backticks...

Just one related factoid: I believe the CMake build defaults to `-O3` anyway.

If necessary, [AtomicLevels](https://github.com/JuliaAtoms/AtomicLevels.jl/) can easily generate the CSLs for comparison & testing various argument combinations. E.g.: ```julia using AtomicLevels term(c::CSF) = last(c.terms) # reference configuration: configuration = c"4f11 6s" #...

Thanks for the report, I can reproduce it with e.g. this input to `rmcdhf`: ``` y ! Default settings 1-40 1-110 1-156 1-173 1-160 1-127 88 52 1-15 1-9 1-2...

I'll reopen this, as this is something that could be fixed at some point.

> but should be put on our ever-growing to-do list That's what the issue tracker is for, so reopening :slightly_smiling_face: I think there are two actionable points here: 1. Make...

Keeping the code compatible with _newer_ versions of dependent libraries is a good thing, if possible. I assume that we're currently officially targeting OpenMPI 2, but e.g. Ubuntu 18.10 shipped...

> Does [INCLUDE 'mpif.h'] work with the latest OpenMPI 4? According to the docs, [`mpif.h` is still supported in OpenMPI 4](https://www.open-mpi.org/doc/current/man1/mpifort.1.php#toc5). FWIW, I can also confirm that the issue does...