-
Notifications
You must be signed in to change notification settings - Fork 899
Cannot compile on Mac with Nag 6.2 #7583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This may be due to nag needing the |
I should say this appears to be mac specific since our group hasn't had issues with this on linux. Maybe there are some issues with case-sensitivity and Mac filesystems so .F90 looks like .f90? |
On Linux, Assuming any fortran file can be preprocessed by NAG compiler via the
and see if it helps |
Was able to compile and successfully run |
I agree this is something that should be handled automatically. Do you have any possibility to run the same test on Linux? |
.F90 files are preprocessed by gfortran and other compilers. NAG compilers only preprocess .{ff,ff90,ff95} files, and the -fpp flag is required to process .F90 files. Fixes open-mpi#7583 Signed-off-by: Gilles Gouaillardet <[email protected]>
@pbrady could you please give a try to #7584? you can manually download the patch at https://github.com/open-mpi/ompi/pull/7584.patch and apply it vs the 4.0.3 sources, and then run This should automatically add the |
@ggouaillardet I tested the patch and was able to compile successfully with the following config: ../configure FC=nagfor Your patch is correctly adding On linux we build with nagfor without explicitly specifying |
Let's make sure it doesn't screw up x86_64 platforms. There NAG passes '.F90' source files through the preprocessor automatically |
@nncarlson Are you going to test the patch on a linux box? |
I was going to let you test it :-) but I guess I can. What exactly should I apply the patch to? Is the latest 4.0.x release good enough, or do I need to clone the repo? |
Autotools builds character and I think I acquired enough yesterday to last awhile. I used the 4.0.3 src tarball and applied the patch via |
Uh, actually would you mind testing it? Is the VPN usable for you to the petaca machines? I'd test with both NAG 6.2 and 7.0 just to be sure. |
I appear to be cursed with a decent VPN connection today... I'll report back in a bit |
I applied the patch and was able to successfully configure, compile and check openmpi with nag6.2 and 7.0 on linux. @ggouaillardet This patch fixes my issues on mac and does not cause any problems on linux. |
.F90 files are preprocessed by gfortran and other compilers. NAG compilers only preprocess .{ff,ff90,ff95} files, and the -fpp flag is required to process .F90 files. Fixes open-mpi#7583 Signed-off-by: Gilles Gouaillardet <[email protected]> (cherry picked from commit a2c711b)
FWIW, the patch is not NAG nor OSX specific, and was designed not to break existing environments.
|
.F90 files are preprocessed by gfortran and other compilers. NAG compilers only preprocess .{ff,ff90,ff95} files, and the -fpp flag is required to process .F90 files. Fixes open-mpi#7583 Signed-off-by: Gilles Gouaillardet <[email protected]> (cherry picked from commit a2c711b)
I'm on MacOS Catalina and attempting to use Nag6.2 as the fortran compiler to build Open MPI v4.0.3 (source tarball). I have tried using the system clang compilers as well as gcc/g++ 9.3 from homebrew. If I use gfortran from homebrew then open mpi compiles without issue so Nag appears to be the culprit here.
The configure step appears to be successful and I've attached the config.log.
make
is able to run for quite some time but I keep getting the following error:I get the same errors when trying to compile Open MPI v3.1.5.
Any advice on how to fix this would be greatly appreciated.
The text was updated successfully, but these errors were encountered: