Hi Alan,
> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Saturday, March 05, 2016 1:11 AM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] Fortran callback progress
>
> On 2016-03-04 14:33-0800 Alan W. Irwin wrote:
>
> > For convenient complete testing of Fortran while avoiding additional
> > testing of other components of PLplot I would recommend running
> >
> > scripts/comprehensive_test.sh --cmake_added_options
> > "-DDEFAULT_NO_DEVICES=ON -DPLD_ps=ON -
> DDEFAULT_NO_BINDINGS=ON
> > -DENABLE_f95=ON -DPL_DOUBLE=OFF" --do_test_interactive no
>
> Oops! That option should read -DPL_DOUBLE=ON or else don't specify -
> DPL_DOUBLE at all (since ON is the default).
>
Alas, I tried that this weekend: somehow CMake gets confused. I have stared at
the error messages, but I can make heads nor tails of the cause.
Here is what I did:
1. I added the directory containing MinGW-w64's sh.exe to the path, so that
the shell script would be run properly
2. I invoked the script like this:
../plplot-git/scripts/comprehensive_test.sh --generator_string "NMake
Makefiles" --do_clean_as_you_go yes --do_test_interactive no
--do_test_traditional_install_tree yes --cmake_added_options
"-DTCL_INCLUDE_PATH=/usr/include" --cmake_added_options "-DENABLE_ada=OFF
-DENABLE_octave=OFF" --do_ctest no --build_command "nmake"
--cmake_added_options "-DCMAKE_Fortran_COMPILER=ifort"
to make sure the Intel Fortran compiler is selected ("NMake Makefiles" was not
enough). It took some experimenting ;).
The error report shows the confusion:
-- The Fortran compiler identification is unknown
-- Check for working Fortran compiler: C:/Program Files (x86)/Intel/Composer XE
2015/bin/intel64/ifort.exe
-- Check for working Fortran compiler: C:/Program Files (x86)/Intel/Composer XE
2015/bin/intel64/ifort.exe -- broken
CMake Error at
D:/cmake3.4.3/share/cmake-3.4/Modules/CMakeTestFortranCompiler.cmake:54
(message):
The Fortran compiler "C:/Program Files (x86)/Intel/Composer XE
2015/bin/intel64/ifort.exe" is not able to compile a simple test program.
It fails with the following output:
Change Dir:
D:/plplot-svn/comprehensive_test_disposeable/shared/noninteractive/build_tree/CMakeFiles/CMakeTmp
Run Build Command:"nmake" "/NOLOGO" "cmTC_a824d\fast"
"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\BIN\amd64\nmake.exe" -f CMakeFiles\cmTC_a824d.dir\build.make
/nologo -L CMakeFiles\cmTC_a824d.dir\build
Building Fortran object
CMakeFiles/cmTC_a824d.dir/testFortranCompiler.f.obj
C:\PROGRA~2\Intel\COMPOS~4\bin\intel64\ifort.exe -c
D:\plplot-svn\comprehensive_test_disposeable\shared\noninteractive\build_tree\CMakeFiles\CMakeTmp\testFortranCompiler.f
-o CMakeFiles\cmTC_a824d.dir\testFortranCompiler.f.obj
Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on
Intel(R) 64, Version 15.0.1.148 Build 20141023
Copyright (C) 1985-2014 Intel Corporation. All rights reserved.
Linking Fortran executable cmTC_a824d.exe
C:\PROGRA~2\Intel\COMPOS~4\bin\intel64\ifort.exe
"CMakeFiles\cmTC_a824d.dir\testFortranCompiler.f.obj" -o cmTC_a824d.exe
Intel(R) Visual Fortran Intel(R) 64 Compiler XE for applications running on
Intel(R) 64, Version 15.0.1.148 Build 20141023
Copyright (C) 1985-2014 Intel Corporation. All rights reserved.
link: unknown option -- s
Try 'link --help' for more information.
NMAKE : fatal error U1077:
'C:\PROGRA~2\Intel\COMPOS~4\bin\intel64\ifort.exe' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'
Stop.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
cmake/modules/fortran.cmake:44 (enable_language)
cmake/modules/plplot.cmake:481 (include)
CMakeLists.txt:136 (include)
(several empty lines eluded)
If you want I can send you the tar file with all details of the process, but I
am particularly puzzled by the message from the linker that it knows no option
"s" and what is more the Intel Fortran compiler is invoked with an option "-o
name-of-executable", which is not the proper option to set the name of the
executable (it should be -exe:name-of-executable).
Anyway, I concluded that that was not a viable route.
Regards,
Arjen
DISCLAIMER: This message is intended exclusively for the addressee(s) and may
contain confidential and privileged information. If you are not the intended
recipient please notify the sender immediately and destroy this message.
Unauthorized use, disclosure or copying of this message is strictly prohibited.
The foundation 'Stichting Deltares', which has its seat at Delft, The
Netherlands, Commercial Registration Number 41146461, is not liable in any way
whatsoever for consequences and/or damages resulting from the improper,
incomplete and untimely dispatch, receipt and/or content of this e-mail.
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
