My mistake, I missed a portion of the directory in the second one. The command -I "dir1" -I "dir2" Worked correctly. Thank you very much Jonathan! ~J On 8/27/12, Jason Clark <jclark@xxxxxxxxx> wrote: > Jonathan, > > Yes that worked I changed my statement to: > > gfortran -I "c:\program files\aspentech\aspen plus > 2006.5\engine\commons" -xf77-cpp-input usrkpg2.f > > And it now works for all the common files in that directory. The new > issue is that there are common files that must be included located in > a different directory. I tried: > > -I "dir1" -I "dir2" which did not work, and > > -I "dir1" "dir2" and that did not work either. I am guessing there is > some simple syntax thing I have wrong here. > > Thanks again! > > ~J > > On 8/27/12, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote: >> On 27 August 2012 19:38, Jason Clark wrote: >>> Jonathan, >>> >>> As you suggested I tried typing in the following: >>> >>> gfortran -I c:/programfiles/aspentech/aspenplus2006.5/engine/commons >>> -xf77-cpp-input usrkpg2.f >>> >>> And got the same error abour the missing file back. I also noticed >>> that if I subsitute in: >>> >>> "z:/" instead of the "c:/..." when no z drive exists does not come >>> back with any error. I am wondering if the preprocessor is not getting >>> to the correct folder. When I try typing in the location using >>> "Program Files" instead of "programfiles" it gives me an error about >>> not finding the directory seemingly due to the space. >> >> You'd need to surround a pathname in quotes if it has spaces, I >> believe that's true on Windows as well as unix-like environments. And >> if you're using the Windows command line you need to use backslashes >> not forward slashes (if you're using Cygwin that might not apply.) >> >
