(0038865)
Brad King (manager)
2015-06-01 09:05

There may be more information in CMakeFiles/CMake*.log about the attempt made to identify the compiler. Please take a look at those files to see if they show the problem.

(0038872)
Paul Durack (reporter)
2015-06-01 19:22

I did take a look at both the CMakeOutput.log and CMakeError.log - is there anything specifically that I'm searching for?

I also tried setting the env var "FC" to /usr/bin/gfortran however that didn't seem to solve the issue..

(0038874)
Brad King (manager)
2015-06-02 09:06

Please attach the log files here.

(0038876)
Paul Durack (reporter)
2015-06-02 23:33
edited on: 2015-06-03 10:53

And here you go"

*****
CMakeError.log:
Looking for a Fortran compiler failed with the following output:
-- The Fortran compiler identification is unknown
CMake Error at CMakeLists.txt:2 (project):
  No CMAKE_Fortran_COMPILER could be found.

  Tell CMake where to find the compiler by setting either the environment
  variable "FC" or the CMake cache entry CMAKE_Fortran_COMPILER to the full
  path to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "/home/duro/uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles/CMakeOutput.log".
See also "/home/duro/uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles/CMakeError.log".

(0038878)
Brad King (manager)
2015-06-03 10:57

Re 0015598:0038876: Thanks. I edited it down to the relevant portion.

This is actually in a test project built via try_compile to determine whether a Fortran compiler can be detected. We'll have to look at the log for that one. Please use the "Upload File" section on this page to attach the "/home/duro/uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles/CMakeError.log" file.

(0038888)
Paul Durack (reporter)
2015-06-06 12:34

Brad, apologies for the delay. You should now have access to both the original log files along with their equivalents sourced from the uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles subdir

(0038895)
Brad King (manager)
2015-06-08 10:41

Re 0015598:0038888: Thanks. The CheckFortran-CMakeFiles-CMakeError.log shows that the compiler was not found there:

Compiler: CMAKE_Fortran_COMPILER-NOTFOUND

Let's try to reproduce this in a simpler test case. Create a fresh source tree containing just a CMakeLists.txt file with:

cmake_minimum_required(VERSION 3.0)
project(Issue15598 Fortran)

Then run CMake to configure that project and attach the log files here.

(0038913)
Paul Durack (reporter)
2015-06-11 21:40

Apologies for the delay Brad, it seems things worked fine:

duro@duro-vm:~/cmake-build$ cmake ./
-- The Fortran compiler identification is GNU
-- Check for working Fortran compiler: /usr/bin/f95
-- Check for working Fortran compiler: /usr/bin/f95 -- works
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Checking whether /usr/bin/f95 supports Fortran 90
-- Checking whether /usr/bin/f95 supports Fortran 90 -- yes
-- Configuring done
-- Generating done
-- Build files have been written to: /home/duro/cmake-build

I've attached the output CMakeFiles/CMakeOutput.log above

(0038916)
Paul Durack (reporter)
2015-06-12 14:44

Brad, just for completeness the CMakeLists.txt file for the project I'm trying to build contained this in the first 10 lines:

*****
#=============================================================================
cmake_minimum_required(VERSION 2.8.8 FATAL_ERROR)

if ("${CMAKE_VERSION}" VERSION_LESS "2.8.12")
message(WARNING "Your CMake version is ${CMAKE_VERSION} which is depreciated for UV-CDAT. The recommended minimum CMake version is 2.8.12. Using older versions can result in build errors particularly with Xcode 5")
endif()

# Project name and initial checks
#=============================================================================
project(cdat)
*****

I wonder if this is tripping over cmake v3.0.2?

(0038925)
Brad King (manager)
2015-06-15 09:23

Re 0015598:0038916: Since it works in the small test project and not under UV-CDAT then something in between must be triggering this problem. The lines you quoted should not affect this because they don't try to enable Fortran yet. You could try stripping the outer project down. Be sure to keep in the part that tries enabling Fortran inside a try_compile.

(0039211)
Paul Durack (reporter)
2015-07-31 13:58

Brad, apologies for dropping this.. I've just managed to get UV-CDAT compiling, and it appears was likely due to a dependency that I hadn't installed.

I'm a little unsure how it has now been resolved, but I no longer have the issue described above.

Thanks,

P

(0039212)
Brad King (manager)
2015-07-31 14:32

Re 0015598:0039211: Okay, thanks for reporting back. If you do manage to reproduce it again please post back here with instructions.

(0040101)
Robert Maynard (manager)
2016-01-04 11:51

Closing resolved issues that have not been updated in more than 4 months.

Notes
(0038865) Brad King (manager) 2015-06-01 09:05	There may be more information in CMakeFiles/CMake*.log about the attempt made to identify the compiler. Please take a look at those files to see if they show the problem.

(0038872) Paul Durack (reporter) 2015-06-01 19:22	I did take a look at both the CMakeOutput.log and CMakeError.log - is there anything specifically that I'm searching for? I also tried setting the env var "FC" to /usr/bin/gfortran however that didn't seem to solve the issue..

(0038874) Brad King (manager) 2015-06-02 09:06	Please attach the log files here.

(0038876) Paul Durack (reporter) 2015-06-02 23:33 edited on: 2015-06-03 10:53	And here you go" ***** CMakeError.log: Looking for a Fortran compiler failed with the following output: -- The Fortran compiler identification is unknown CMake Error at CMakeLists.txt:2 (project): No CMAKE_Fortran_COMPILER could be found. Tell CMake where to find the compiler by setting either the environment variable "FC" or the CMake cache entry CMAKE_Fortran_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. -- Configuring incomplete, errors occurred! See also "/home/duro/uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles/CMakeOutput.log". See also "/home/duro/uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles/CMakeError.log".

(0038878) Brad King (manager) 2015-06-03 10:57	Re 0015598:0038876: Thanks. I edited it down to the relevant portion. This is actually in a test project built via try_compile to determine whether a Fortran compiler can be detected. We'll have to look at the log for that one. Please use the "Upload File" section on this page to attach the "/home/duro/uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles/CMakeError.log" file.

(0038888) Paul Durack (reporter) 2015-06-06 12:34	Brad, apologies for the delay. You should now have access to both the original log files along with their equivalents sourced from the uvcdat-build/CMakeFiles/CheckFortran/CMakeFiles subdir

(0038895) Brad King (manager) 2015-06-08 10:41	Re 0015598:0038888: Thanks. The CheckFortran-CMakeFiles-CMakeError.log shows that the compiler was not found there: Compiler: CMAKE_Fortran_COMPILER-NOTFOUND Let's try to reproduce this in a simpler test case. Create a fresh source tree containing just a CMakeLists.txt file with: cmake_minimum_required(VERSION 3.0) project(Issue15598 Fortran) Then run CMake to configure that project and attach the log files here.

(0038913) Paul Durack (reporter) 2015-06-11 21:40	Apologies for the delay Brad, it seems things worked fine: duro@duro-vm:~/cmake-build$ cmake ./ -- The Fortran compiler identification is GNU -- Check for working Fortran compiler: /usr/bin/f95 -- Check for working Fortran compiler: /usr/bin/f95 -- works -- Detecting Fortran compiler ABI info -- Detecting Fortran compiler ABI info - done -- Checking whether /usr/bin/f95 supports Fortran 90 -- Checking whether /usr/bin/f95 supports Fortran 90 -- yes -- Configuring done -- Generating done -- Build files have been written to: /home/duro/cmake-build I've attached the output CMakeFiles/CMakeOutput.log above

(0038916) Paul Durack (reporter) 2015-06-12 14:44	Brad, just for completeness the CMakeLists.txt file for the project I'm trying to build contained this in the first 10 lines: *** #============================================================================= cmake_minimum_required(VERSION 2.8.8 FATAL_ERROR) if ("${CMAKE_VERSION}" VERSION_LESS "2.8.12") message(WARNING "Your CMake version is ${CMAKE_VERSION} which is depreciated for UV-CDAT. The recommended minimum CMake version is 2.8.12. Using older versions can result in build errors particularly with Xcode 5") endif() # Project name and initial checks #============================================================================= project(cdat) *** I wonder if this is tripping over cmake v3.0.2?

(0038925) Brad King (manager) 2015-06-15 09:23	Re 0015598:0038916: Since it works in the small test project and not under UV-CDAT then something in between must be triggering this problem. The lines you quoted should not affect this because they don't try to enable Fortran yet. You could try stripping the outer project down. Be sure to keep in the part that tries enabling Fortran inside a try_compile.

(0039211) Paul Durack (reporter) 2015-07-31 13:58	Brad, apologies for dropping this.. I've just managed to get UV-CDAT compiling, and it appears was likely due to a dependency that I hadn't installed. I'm a little unsure how it has now been resolved, but I no longer have the issue described above. Thanks, P

(0039212) Brad King (manager) 2015-07-31 14:32	Re 0015598:0039211: Okay, thanks for reporting back. If you do manage to reproduce it again please post back here with instructions.

(0040101) Robert Maynard (manager) 2016-01-04 11:51	Closing resolved issues that have not been updated in more than 4 months.

Issue History
Date Modified	Username	Field	Change
2015-05-31 17:07	Paul Durack	New Issue
2015-06-01 09:05	Brad King	Note Added: 0038865
2015-06-01 19:22	Paul Durack	Note Added: 0038872
2015-06-02 09:06	Brad King	Note Added: 0038874
2015-06-02 23:33	Paul Durack	Note Added: 0038876
2015-06-03 10:53	Brad King	Note Edited: 0038876
2015-06-03 10:57	Brad King	Note Added: 0038878
2015-06-06 12:25	Paul Durack	File Added: CMakeError.log
2015-06-06 12:26	Paul Durack	File Added: CMakeOutput.log
2015-06-06 12:32	Paul Durack	File Added: CheckFortran-CMakeFiles-CMakeError.log
2015-06-06 12:32	Paul Durack	File Added: CheckFortran-CMakeFiles-CMakeOutput.log
2015-06-06 12:34	Paul Durack	Note Added: 0038888
2015-06-08 10:41	Brad King	Note Added: 0038895
2015-06-11 21:38	Paul Durack	File Added: CMakeFiles-CMakeOutput.log
2015-06-11 21:40	Paul Durack	Note Added: 0038913
2015-06-12 14:44	Paul Durack	Note Added: 0038916
2015-06-15 09:23	Brad King	Note Added: 0038925
2015-07-31 13:58	Paul Durack	Note Added: 0039211
2015-07-31 14:32	Brad King	Note Added: 0039212
2015-07-31 14:32	Brad King	Status	new => resolved
2015-07-31 14:32	Brad King	Resolution	open => unable to reproduce
2016-01-04 11:51	Robert Maynard	Note Added: 0040101
2016-01-04 11:51	Robert Maynard	Status	resolved => closed

Relationships