RE: [CMake] Windows ifort problems, possible bug
Hi Bill, I have checked the stuff. Everything is ok. Now I can build a nmake project without any touch.exe. Alin I have changed cmake to no longer use touch for this. A fixed version can be found here: http://www.cmake.org/files/vCVS/cmake-2.5.20071205-win32-x86.exe If you have the time, I would appreciate it if you could test it in a shell that does not have touch and verify that it works for you. Thanks. -Bill "...if the universities will not study useless subjects, who will?" G. F. Fitzgerald, Nature, 45/46, 392 (1892) __ Mr. Alin M. ELENA Atomistic Simulation Centre School of Mathematics and Physics Queen's University Belfast Office: +44 (0)28 9097 1428 Fax: +44 (0)28 9097 5359 http://titus.phy.qub.ac.uk/group/Alin/ [EMAIL PROTECTED] [EMAIL PROTECTED] __ ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Windows ifort problems, possible bug
Alan W. Irwin wrote: On 2007-12-05 08:09- Alin M Elena wrote: Hi Bill, That was the problem. Even if in the shell (PowerShell) I had a touch available loaded through the profile script cmake wanted a proper one. Fixed it now and nmake build is ok. Bill, if you are concerned about this dependency on touch, one way around it would be to create a cmake -E equivalent to touch. I believe that extra cmake -E feature would be useful not only in this case, but also in general. That is what I did Alin verified that it worked fine from here: http://www.cmake.org/files/vCVS/cmake-2.5.20071205-win32-x86.exe -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Windows ifort problems, possible bug
On 2007-12-05 08:09- Alin M Elena wrote: Hi Bill, That was the problem. Even if in the shell (PowerShell) I had a touch available loaded through the profile script cmake wanted a proper one. Fixed it now and nmake build is ok. Bill, if you are concerned about this dependency on touch, one way around it would be to create a cmake -E equivalent to touch. I believe that extra cmake -E feature would be useful not only in this case, but also in general. Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Windows ifort problems, possible bug
Alin M Elena wrote: Hi Bill, That was the problem. Even if in the shell (PowerShell) I had a touch available loaded through the profile script cmake wanted a proper one. Fixed it now and nmake build is ok. I have changed cmake to no longer use touch for this. A fixed version can be found here: http://www.cmake.org/files/vCVS/cmake-2.5.20071205-win32-x86.exe If you have the time, I would appreciate it if you could test it in a shell that does not have touch and verify that it works for you. Thanks. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Windows ifort problems, possible bug
Hi Bill, That was the problem. Even if in the shell (PowerShell) I had a touch available loaded through the profile script cmake wanted a proper one. Fixed it now and nmake build is ok. Alin "...if the universities will not study useless subjects, who will?" G. F. Fitzgerald, Nature, 45/46, 392 (1892) __ Mr. Alin M. ELENA Atomistic Simulation Centre School of Mathematics and Physics Queen's University Belfast Office: +44 (0)28 9097 1428 Fax: +44 (0)28 9097 5359 http://titus.phy.qub.ac.uk/group/Alin/ [EMAIL PROTECTED] [EMAIL PROTECTED] __ It must not be in your path then... This is the error you are getting: [ 50%] Building Fortran object CMakeFiles/hello.dir/constants.obj 'touch' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'touch' : return code '0x1' It is pretty clear that nmake tries to run touch and does not find it. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Windows ifort problems, possible bug
Alin M Elena wrote: Hi Bill, Got a touch in the shell. It seems that it does not change anything. I have filled a bug report. It must not be in your path then... This is the error you are getting: [ 50%] Building Fortran object CMakeFiles/hello.dir/constants.obj 'touch' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'touch' : return code '0x1' It is pretty clear that nmake tries to run touch and does not find it. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Windows ifort problems, possible bug
Hi Bill, Got a touch in the shell. It seems that it does not change anything. I have filled a bug report. Alin -Original Message- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: 04 December 2007 18:10 To: [EMAIL PROTECTED] Cc: cmake@cmake.org Subject: Re: [CMake] Windows ifort problems, possible bug Looks like cmake requires touch to be on the machine. This is obviously not in the cross platform spirit of CMake. Please create a bug report, and for now the work around will be to install a touch.exe in your path. I checked the source code, and it does expect a touch to be in the path. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Windows ifort problems, possible bug
Alin, Have you checked that your environment is set properly for ifort? Can you build from "cmd" or are you building from the shell provided with the Intel compiler. You can also check the Environment Variables from the System Control Panel? Have you added the path to your ifort libraries to Windows-ifort.cmake? >From my previous message, this is by including the following line to that file: LINK_DIRECTORIES() Have you installed ifort in a directory path that does not contain spaces? Once I did those three things I was able to build using ifort ion Windows. --Danny > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Alin M Elena > Sent: Tuesday, December 04, 2007 10:59 AM > To: cmake@cmake.org > Subject: [CMake] Windows ifort problems, possible bug > > Hi, > > Thank you Alan. > I have reduced the problem to a simpler one. I tend to think > that is a bug. > It may be connected with the one found by Daniel Dunalvy. > > If I create a fortran project with a single file. It > compiles, links and everything is ok. > I have checked with nmake and Visual Studio 8 2005 generators > When I create a fortran project with two files it fails for > both generators > with: > Visual studio > Error 1 error PRJ0019: A tool returned an error code > from "Building > Fortran object test.obj" hello > > PS C:\Users\Alin M Elena\testFortran> nmake > > Microsoft (R) Program Maintenance Utility Version > 8.00.50727.762 Copyright (C) Microsoft Corporation. All > rights reserved. > > Scanning dependencies of target hello > [ 50%] Building Fortran object CMakeFiles/hello.dir/constants.obj > 'touch' is not recognized as an internal or external command, > operable program or batch file. > NMAKE : fatal error U1077: 'touch' : return code '0x1' > Stop. > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft > Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' > Stop. > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft > Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' > Stop. > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft > Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' > Stop. > > If I compile and link by hand in shell everything is ok. > > Here is the listing of the files. > > > > CMakeLists.txt > > Project(hello Fortran) > add_executable(hello > constants.f90 > test.f90) > > > test.f90 > program test > use m_constants > implicit none > print *,one > print *, "hello world" > end program test > > constants.f90 > module m_constants > implicit none > private > integer, parameter, public :: one=1 > > end module m_constants > > > "...if the universities will not study useless subjects, who will?" >G. F. Fitzgerald, Nature, 45/46, > 392 (1892) > __ > Mr. Alin M. ELENA > Atomistic Simulation Centre > School of Mathematics and Physics > Queen's University Belfast > Office: +44 (0)28 9097 1428 > Fax: +44 (0)28 9097 5359 > http://titus.phy.qub.ac.uk/group/Alin/ > [EMAIL PROTECTED] > [EMAIL PROTECTED] > __ > > > ___ > CMake mailing list > CMake@cmake.org > http://www.cmake.org/mailman/listinfo/cmake > > ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Windows ifort problems, possible bug
Alin M Elena wrote: Hi, NMAKE : fatal error U1077: 'touch' : return code '0x1' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 8\VC\BIN\nmake.exe"' : return code '0x2' Stop. Looks like cmake requires touch to be on the machine. This is obviously not in the cross platform spirit of CMake. Please create a bug report, and for now the work around will be to install a touch.exe in your path. I checked the source code, and it does expect a touch to be in the path. -Bill ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
