IMPLICIT NONE (TYPE,EXTERNAL)

157 views
Skip to first unread message

Morteza

unread,
Apr 6, 2021, 7:26:17 AM4/6/21
to FDS and Smokeview Discussions
Hi Kevin,

I no longer can compile the code since (TYPE,EXTERNAL) is added. What could be the solution (except for removing them manually)?

BR,

IMPLICIT NONE.JPG

Kevin McGrattan

unread,
Apr 6, 2021, 7:30:30 AM4/6/21
to fds...@googlegroups.com
FDS now complies with the 2018 Fortran standard. I suggest you upgrade to the oneAPI series of Intel compilers and tools. They are free, and they are what we now use.

Morteza

unread,
Apr 16, 2021, 4:45:12 AM4/16/21
to FDS and Smokeview Discussions
Kevin,

I now have both packages of oneAPI installed, along with the VS19.
When I try compiling through impi_intel_win_64, I receive these error messages:

MPI_F08.JPG

Simo also received similar errors while compiling on his Win machine.

Seems like it can find the IFORT.exe to work with, but fails to find INCLUDE paths
My initial guess was the environment variable paths on my Windows machine, but failed to fix it.

Have you ever encountered such a problem?

Morteza

unread,
Apr 16, 2021, 4:48:32 AM4/16/21
to FDS and Smokeview Discussions
Here are what I have as path variables:

path.JPG

Randy McDermott

unread,
Apr 16, 2021, 9:13:49 AM4/16/21
to FDS and Smokeview Discussions
I would make sure that *everything* is up to date.  For example, on OSX we had to make sure that XCode was all up-to-date before the libraries were present.

--
You received this message because you are subscribed to the Google Groups "FDS and Smokeview Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/fb7e1351-0e94-4cba-9c2c-bebded91de8cn%40googlegroups.com.

Kevin McGrattan

unread,
Apr 16, 2021, 9:28:31 AM4/16/21
to fds...@googlegroups.com
I'm still using the 2021.1 version of the compiler. I have not tried the latest. Have you successfully compiled using any version of oneAPI?

Glenn Forney

unread,
Apr 16, 2021, 9:30:00 AM4/16/21
to fds...@googlegroups.com
did you reboot your computer after installing your compilers?  

open up a new command shell then type
set

look for an environment variable named I_MPI_ONEAPI_ROOT

if you don't see it then your compiler installation is not complete.  This environment variable is defined by the Intel installers and used by the fds Build scripts

also
cd into fds\Build\Scripts and type
setup_intel_compilers





--
Glenn Forney

Glenn Forney

unread,
Apr 16, 2021, 11:17:06 AM4/16/21
to FDS and Smokeview Discussions
also make sure you've updated your fds repo to the latest revision.

Morteza

unread,
Apr 19, 2021, 3:02:23 AM4/19/21
to FDS and Smokeview Discussions
"open up a new command shell then type
set"
-- I did, and the environment variable I_MPI_ONEAPI_ROOT exists.

"cd into fds\Build\Scripts and type
setup_intel_compilers"
-- When I did that, I received the following error:
"*** Error: Intel compiler environment variable, IFORT_COMPILER, not defined."
"    Intel compilers probably not installed."

Instead of double-clicking on the make_fds.bat file, I followed a workaround and was able to compile flawlessly.
I used the "Intel oneAPI command prompt for Intel 64 for Visual Studio 2019" and ran the make_fds batch file from there.
Seems like oneAPI needs to configure the environment for VS through its own command prompt each time, at least on my machine.
Reply all
Reply to author
Forward
0 new messages