dear Brad, thanks for testing it on your side and also for the suggestions! 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 Can you see something possibly related in there? thank you & best wishes, radovan On Thu, Jul 2, 2015 at 3:30 PM Brad King <brad.k...@kitware.com> wrote: > On 07/02/2015 04:14 AM, Radovan Bast wrote: > > We have observed a changed and surprising behavior in CMake 3.3.0-rc3 > > with Fortran module dependency scanning and preprocessing compared to > > earlier CMake versions (for instance 3.2.3). > > I don't recall any changes related to this since 3.2. I also cannot > reproduce the problem with the example you provided. > > > It seems that Fortran dependencies are scanned prior to pre-processing. > > CMake does its own approximate preprocessing for dependency scanning. > This hasn't changed in a long time. > > Can you please provide a more complete example to reproduce this? > Or, if you can consistently reproduce it locally please try bisecting > our Git history between 3.2 and 3.3 to see if you can find the commit > that introduced the problem. > > Thanks, > -Brad > >
-- 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
