Jim Dishaw <[EMAIL PROTECTED]> writes: > "Alan W. Irwin" <[EMAIL PROTECTED]> writes: > >> On 2007-10-21 21:49-0400 Jim Dishaw wrote: >>> >>> The problem is that CMake sees the Intel Visual Fortran installation and >>> sets the compiler flag "/DIVF" and that causes the GNU compiler to >>> fail. >> >> Jim, please correct me if you have a different experience, but my belief is >> the environment variable approach is going to set the fortran compiler and >> its options completely consistently so there should be no inconsistent extra >> options like "/DIVF" unless the build was done starting from a dirty build >> tree. >> > > The only way that /DIVF gets set is if the TARGET_FORTRAN variable is > set to IVF. The TARGET_FORTRAN variable is set in > cmake/modules/fortran.cmake, where CMAKE_Fortran_COMPILER is checked > against the substring ".*/ifort.*" > > If the environment variable FC is set, does that override the normal > compiler check and cause CMAKE_Fortran_COMPILER to be set to whichever > compiler FC is set to? Perhaps there was a dirty build directory? I > can try to run a test and see how the variables are set (I have a > machine with Intel Fortran and cygwin+gnu compiler). I'll report back > with the results. > >> Jim, what happens if you try that simple case on Cygwin for 5.8.0-RC1? >
I downloaded the 5.8.0-RC1 source tarball and followed the build instructions on the Wiki for cygwin. First, I was not able to get things working without specifying -DBUILD_SHARED_LIBS=OFF. Everything would build correctly, however when I attempted to run the executables, nothing would happen. With the -DBUILD_SHARED_LIBS=OFF I was able to build and run the executables. I then added the Intel Fortran compiler to the beginning of the path and the CMake failed when it tried to use the Intel compiler in the cygwin environment. The Intel compiler fails because CMake is passing arguments using Unix style paths, which are interpreted as arguments because path seperators in Unix are "/" and Windows uses "/" as command switches. I then ran CMake again, without deleting anything, and CMake then proceeded to create the Makefiles. I noticed that TARGET_FORTRAN was set to IVF and the ENABLE_f77 was ON even though CMake did not successfully test the Intel Fortran compiler. After giving the make command, the libplplot and libplplotcxd libraries were built. The libplplotf77cd library failed. If you then go to the examples directory, the c and c++ examples build correctly with a make command. The f77 examples fails to build. If you start with a clean directory and specify FC=g77 then everything builds correctly with Intel Fortran in the path and TARGET_FORTRAN is blank (as it should be). I guess this behavior should be documented in the Wiki and INSTALL notes or the cmake files should disable F77 if the the test fails when cmake is run. -jd ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
