problems with gfortran module creation and "make -j" about conduit HOT 7 CLOSED

I think the problem is cropping up in unit testing. The solution may simply be to create a lib for fruit AND the fortran gtest driver.

from conduit.

This could also bug specific to gfortran 4.9 and 4.9.1
http://stackoverflow.com/questions/27281158/fortran-90-gfortran-fatal-error-cant-rename-module-file-exists
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62215

from conduit.

closing, I don't see this any more on OSX 10.11 using gfortran 6.1. Assuming this was resolved by the compiler update.

from conduit.

seeing with gfortran 5 (or even 7) so this isn't just the 4.9 bug.

Seems like a chicken vs egg issue. Object libs might help, or setting more fortran flags:

https://stackoverflow.com/questions/43917443/fortran-module-files-not-found-by-cmake

from conduit.

https://gitlab.kitware.com/cmake/cmake/issues/17525

from conduit.

Try not using a single Fortran_MODULE_DIRECTORY dir, by tweaking
SetupFortran.cmake:

    set(CMAKE_Fortran_MODULE_DIRECTORY ${PROJECT_BINARY_DIR}/fortran)
      
      # make sure the fortran compiler can see the module files it
      # generates
      include_directories(${CMAKE_Fortran_MODULE_DIRECTORY})

from conduit.

finally got to the bottom of this.

It was a very simple error: I had a copy and paste typo in one of the test modules leading to a name collision.

The t_conduit_node_obj test, was defining a module t_conduit_node instead of t_conduit_node_obj. Since the t_conduit_node test also defines the t_conduit_node module -- they would stomp on each other when compiled in parallel.

from conduit.