* [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include
@ 2024-03-16 20:25 meator
2024-03-16 20:57 ` Open MPI: mpif90 " oreo639
` (11 more replies)
0 siblings, 12 replies; 13+ messages in thread
From: meator @ 2024-03-16 20:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
New issue by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/49322
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.21_1 x86_64 GenuineIntel uptodate hold rrrdDFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
### Package(s) Affected
openmpi-5.0.2_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Having the following code:
```fortran
program main
#include "mpif.h"
integer ierr
call mpi_init(ierr)
end
```
I expect it to compile with
```
mpif90 code.F90
```
Note that I didn't make up this code, it comes from a configure script of a library I'd like to package which tries to test whether fortran compiler works by compiling the aforementioned code.
### Actual behaviour
It doesn't compile. It however compiles with
```
mpif90 code.F90 -I/usr/include
```
To my knowledge (and please correct me if I'm wrong), `mpif90` (like all other MPI wrappers which link to `/usr/bin/opal_wrapper`) should wrap the underlying compiler while providing **all** flags needed for compiling with MPI.
```
mpif90 --showme
```
shows
```
gfortran -I/usr/lib64 -Wl,-rpath -Wl,/usr/lib64 -Wl,--enable-new-dtags -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi
```
which makes no mention of `/usr/include`.
I don't have proof of this, but I believe this is a regression, because it used to work in the past, so I assume an `openmpi` update broke it.
I've done some tests and it works without `-I/usr/include` on a Debian Docker container. Debian packages openmpi quite differently, its `--showme` looks like this:
```
gfortran -I/usr/lib/x86_64-linux-gnu/openmpi/lib/../../fortran/gfortran-mod-15/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr/lib/x86_64-linux-gnu/openmpi/lib/fortran/gfortran -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi -lopen-rte -lopen-pal -lhwloc -levent_core -levent_pthreads -lm -lz
```
but it shows that it should work out of the box I believe.
Ping maintainer @ahesford
### Steps to reproduce
Mentioned above.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
@ 2024-03-16 20:57 ` oreo639
2024-03-16 21:00 ` oreo639
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 20:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002129504
Comment:
> Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/open-mpi/ompi/issues/12257
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
2024-03-16 20:57 ` Open MPI: mpif90 " oreo639
@ 2024-03-16 21:00 ` oreo639
2024-03-16 21:04 ` oreo639
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 21:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002129504
Comment:
> Does a report exist for this bug with the project's home (upstream) and/or another distro?
> _No response_
https://github.com/open-mpi/ompi/issues/12257
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
2024-03-16 20:57 ` Open MPI: mpif90 " oreo639
2024-03-16 21:00 ` oreo639
@ 2024-03-16 21:04 ` oreo639
2024-03-16 21:36 ` meator
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 21:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002129504
Comment:
> ### Does a report exist for this bug with the project's home (upstream) and/or another distro?
> _No response_
https://github.com/open-mpi/ompi/issues/12257
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (2 preceding siblings ...)
2024-03-16 21:04 ` oreo639
@ 2024-03-16 21:36 ` meator
2024-03-16 21:56 ` ahesford
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: meator @ 2024-03-16 21:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002142800
Comment:
Thanks for including the upstream issue. I haven't noticed that.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (3 preceding siblings ...)
2024-03-16 21:36 ` meator
@ 2024-03-16 21:56 ` ahesford
2024-03-16 22:05 ` oreo639
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ahesford @ 2024-03-16 21:56 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002150669
Comment:
Note that most C and C++ compilers look in `/usr/include` *implicitly*. Thus, `mpicc` should work automatically without the wrapper passing `-I/usr/include`. (Indeed, `mpicc --showme` shows no include arguments at all.) I'm not sure `gfortran` makes (or should make) the same assumption. Also note that the include file itself, `mpif.h`, seems to recommend explicitly passing `-I$OMPI_HOME/include` for a suitably defined `$OMPI_HOME`.
Let's see how the upstream issue shakes out before trying to resolve this regression.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (4 preceding siblings ...)
2024-03-16 21:56 ` ahesford
@ 2024-03-16 22:05 ` oreo639
2024-03-16 22:05 ` oreo639
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 22:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002153452
Comment:
> Let's see how the upstream issue shakes out before trying to resolve this regression.
It's from January with no response from the maintainers and the person who made the issue already [worked around the issue on Arch Linux's side](https://gitlab.archlinux.org/archlinux/packaging/packages/openmpi/-/blob/main/PKGBUILD#L51-54), so I'm not sure there will be much movement there.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (5 preceding siblings ...)
2024-03-16 22:05 ` oreo639
@ 2024-03-16 22:05 ` oreo639
2024-03-16 22:06 ` oreo639
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 22:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002153452
Comment:
> Let's see how the upstream issue shakes out before trying to resolve this regression.
It's from January with no response from the maintainers and the person who made the issue already [worked around the issue on Arch Linux's side](https://gitlab.archlinux.org/archlinux/packaging/packages/openmpi/-/blob/main/PKGBUILD#L51-54), so I'm not sure there will be much movement from that side.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (6 preceding siblings ...)
2024-03-16 22:05 ` oreo639
@ 2024-03-16 22:06 ` oreo639
2024-03-16 22:26 ` oreo639
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 22:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002153452
Comment:
> Let's see how the upstream issue shakes out before trying to resolve this regression.
It's from January with no response from the maintainers and the person who made the issue already [worked around the issue on Arch Linux's side](https://gitlab.archlinux.org/archlinux/packaging/packages/openmpi/-/blob/main/PKGBUILD#L51-54), so I'm not sure there will be much movement from that side either.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (7 preceding siblings ...)
2024-03-16 22:06 ` oreo639
@ 2024-03-16 22:26 ` oreo639
2024-03-17 0:53 ` oreo639
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-16 22:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002153452
Comment:
> Let's see how the upstream issue shakes out before trying to resolve this regression.
It's from January with no response from the maintainers and the person who made the issue already [worked around the issue on Arch Linux's side](https://gitlab.archlinux.org/archlinux/packaging/packages/openmpi/-/blob/main/PKGBUILD#L51-54), so I'm not sure there will be much movement atm.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (8 preceding siblings ...)
2024-03-16 22:26 ` oreo639
@ 2024-03-17 0:53 ` oreo639
2024-04-12 12:27 ` ahesford
2024-04-12 12:47 ` [ISSUE] [CLOSED] " ahesford
11 siblings, 0 replies; 13+ messages in thread
From: oreo639 @ 2024-03-17 0:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2002153452
Comment:
> Let's see how the upstream issue shakes out before trying to resolve this regression.
It's from January with no response from the maintainers and the person who made the issue already [worked around the issue on Arch Linux's side](https://gitlab.archlinux.org/archlinux/packaging/packages/openmpi/-/blob/main/PKGBUILD#L51-54), so I'm not sure there will be much movement as-is.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (9 preceding siblings ...)
2024-03-17 0:53 ` oreo639
@ 2024-04-12 12:27 ` ahesford
2024-04-12 12:47 ` [ISSUE] [CLOSED] " ahesford
11 siblings, 0 replies; 13+ messages in thread
From: ahesford @ 2024-04-12 12:27 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/49322#issuecomment-2051665459
Comment:
I'll pull the Arch patch for 5.0.3 shortly. If, in the future, upstream explicitly rejects this or a similar fix, I'll drop the patch and users will have no choice but to specify `-I/usr/include` for FORTRAN programs.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [ISSUE] [CLOSED] Open MPI: mpif90 doesn't -I/usr/include
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
` (10 preceding siblings ...)
2024-04-12 12:27 ` ahesford
@ 2024-04-12 12:47 ` ahesford
11 siblings, 0 replies; 13+ messages in thread
From: ahesford @ 2024-04-12 12:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
Closed issue by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/49322
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.21_1 x86_64 GenuineIntel uptodate hold rrrdDFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
### Package(s) Affected
openmpi-5.0.2_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/open-mpi/ompi/issues/12257
### Expected behaviour
Having the following code:
```fortran
program main
#include "mpif.h"
integer ierr
call mpi_init(ierr)
end
```
I expect it to compile with
```
mpif90 code.F90
```
Note that I didn't make up this code, it comes from a configure script of a library I'd like to package which tries to test whether fortran compiler works by compiling the aforementioned code.
### Actual behaviour
It doesn't compile. The following error message is shown:
```
/usr/include/mpif.h:56:0:
56 | include 'mpif-config.h'
|
Fatal Error: Cannot open included file 'mpif-config.h'
compilation terminated.
```
It's obvious that it's caused by a missing include. It compiles with
```
mpif90 code.F90 -I/usr/include
```
To my knowledge (and please correct me if I'm wrong), `mpif90` (like all other MPI wrappers which link to `/usr/bin/opal_wrapper`) should wrap the underlying compiler while providing **all** flags needed for compiling with MPI.
```
mpif90 --showme
```
shows
```
gfortran -I/usr/lib64 -Wl,-rpath -Wl,/usr/lib64 -Wl,--enable-new-dtags -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi
```
which makes no mention of `/usr/include`.
I don't have proof of this, but I believe this is a regression, because it used to work in the past, so I assume an `openmpi` update broke it.
I've done some tests and it works without `-I/usr/include` on a Debian Docker container. Debian packages openmpi quite differently, its `--showme` looks like this:
```
gfortran -I/usr/lib/x86_64-linux-gnu/openmpi/lib/../../fortran/gfortran-mod-15/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr/lib/x86_64-linux-gnu/openmpi/lib/fortran/gfortran -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi -lopen-rte -lopen-pal -lhwloc -levent_core -levent_pthreads -lm -lz
```
but it shows that it should work out of the box I believe.
Ping maintainer @ahesford
### Steps to reproduce
Mentioned above.
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2024-04-12 12:47 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-16 20:25 [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include meator
2024-03-16 20:57 ` Open MPI: mpif90 " oreo639
2024-03-16 21:00 ` oreo639
2024-03-16 21:04 ` oreo639
2024-03-16 21:36 ` meator
2024-03-16 21:56 ` ahesford
2024-03-16 22:05 ` oreo639
2024-03-16 22:05 ` oreo639
2024-03-16 22:06 ` oreo639
2024-03-16 22:26 ` oreo639
2024-03-17 0:53 ` oreo639
2024-04-12 12:27 ` ahesford
2024-04-12 12:47 ` [ISSUE] [CLOSED] " ahesford
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).