If you are testing 64-bit ifort, you will have to adjust ifort.cfg so as to invoke Microsoft link, in case cygwin 32-bit link comes first in PATH. Otherwise, you would have to translate a great deal of ifortvars.bat and vcvars32.bat into bash syntax and make your own script. In principle, once you have everything set up, you could shell off a cmd.exe, run ifortvars.bat and then cygwin.bat and so get the usual combined ifort and cygwin bash environment. cygdrive/c/Program Files/Intel/Fortran/Compiler80/IA32/BIN:/cygdrive/c/Program Files/Common Files/Intel/Shared FilĮs/IA32/BIN:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/X11R6/bin:/opt/binĪny thoughts as to what I might be doing wrong here? All rights reserved.įortcom: Severe: No such file or directoryĬompilation aborted for test.f90 (code 1) Intel Fortran Compiler for 32-bit applications, Version 8.1 Build 20040802Z Package ID: w_fc_p_8.1.019Ĭopyright (C) 1985-2004 Intel Corporation. I can get it to build a very simple test program from the command line in the DOS window, after having run ifortvars.bat).īut when I try this in a cygwin bash shell, I get the following ~$ ifort test.f90 I am trying to get the ifort compiler to work undercygwin, but I can't.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |