This is – almost – a piggyback on someone’s previous thread a month ago, “Problems installing PGI Community Edition 17.10”,
The machine is a Windows 10 64 bit system, and I am getting most of the same symptoms. I’ve debugged a bit, and have these insights.
o I followed the very same steps is required, and as listed in the previous post.
o The first time I added in CUDA and other extra features. When it didn’t work, I uninstalled and ran installation again, without any extra features, and it still didn’t work.
o By “didn’t work”, I mean that, whether it was pgcc or pgf90 or pgfortran, well, without arguments, it ran and gave the “no files specified” error message. But if a program source file is specified, the compiler seems to hang, and if I open the Task Manager, I see the compiler process, and it gets larger and larger. (One time I let it run and it got up to 2.5 gigabytes of RAM before I killed it.)
o That other person did not see any Visual Studio integration, and I don’t see it either. No Fortran items in the menus, that sort of thing.
o While the got 32 bit versions of the F77, F90, and F95 compilers, I have 64 bit versions of everything.
o The bash window does close right away. This is because the shortcut calls the BAT file with “C:\Windows\System32\cmd.exe /c C:\PROGRA~1\PGICE\win64\17.10\pgi.bat”, and that PGI.BAT has a couple of references to a " s:\Cygwin " folder. But there is no such drive ( "s:" ) on my system!
o If I modify the PGI.BAT file to point to my very real c:\cygwin folder, the bash window stays open.
Now:
#1
I can understand if Visual Studio was required just to get some utilities (as the previous thread seemed to say) and that Visual Studio doesn’t integrate with the PG compilers. (I am more of a command line person, myself.) So that is not an issue.
#2
The Big Problem – The “doesn’t work” description above is the thing I am trying to get around. When I try to use the compiler (say, PGfortran) as
pgfortran -o helloworld.exe helloworld.f
… it seems to hang, and Task Manager shows a process that grows and grows.
In case the PG compilers were “colliding” with other compilers, I took steps to wipe out the PATH variable before letting the PGI.BAT file set it. There was a LIBRARY_PATH environment variable that I also zilched. That didn’t change anything.
The PGI.BAT file provides access to the VS2015 utilities, because it has the line
set PATH=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64;%PATH%
I will be checking all the other files it seems to want, but if anyone here recognized this problem behavior, please let me know.
Thanks,
OldeFortranAle