dear Brad, SOMEDEF is defined at compile time. Attached is a tarball that contains the CMakeLists.txt which defines SOMEDEF, a main.F90 and a mymodule.F90 which contains the module which is not built prior to building main.F90.
In principle the problem can be reproduced like this: ``` tar xvzf example.tar.gz cd example/ mkdir build cd build/ cmake .. make ``` Thank you for looking into this! Best wishes, radovan On Mon, Jul 6, 2015 at 3:02 PM Brad King <brad.k...@kitware.com> wrote: > On 07/02/2015 06:25 PM, Radovan Bast wrote: > > I can consistently reproduce it locally on 3 different machines (Ubuntu > 14.04 > > and Arch derivative; gfortran 4.8.4 and 5.1.0). > > > > I have Git bisected the history and this is the commit that broke this > > example on my machines: > > > https://github.com/Kitware/CMake/commit/0b945ea9a6a38d1b3ee27cc32afb4268bd571600 > > Thanks for bisecting! > > > Can you see something possibly related in there? > > That change may have accidentally affected the preprocessor definitions > sent to the Fortran compiler. The error message you're seeing is actually > coming from the compiler trying to use the module, so SOMEDEF must be > getting defined. However, without seeing your CMake code I cannot > determine how. > > Can you provide a minimal source tarball that exhibits the problem? > > Thanks, > -Brad >
example.tar.gz
Description: application/gzip
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
