Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Open MPI: mpiff77 doesn't -I/usr/include
Date: Sat, 16 Mar 2024 21:25:54 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49322@inbox.vuxu.org> (raw)

[-- 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.

             reply	other threads:[~2024-03-16 20:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 20:25 meator [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49322@inbox.vuxu.org \
    --to=meator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).