[MacPorts] #55153: armadillo @8.200.1 +arpack: 'mpi.h' file not found

Discussion:

MacPorts

2017-10-23 09:13:26 UTC

#55153: armadillo @8.200.1 +arpack: 'mpi.h' file not found
----------------------------+-----------------------
Reporter: majoc-at-astro | Owner:
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.4.2
Keywords: | Port: armadillo
----------------------------+-----------------------
Log from last Friday's build run to be attached. Here's the top bit:
{{{
:info:build In file included from
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_armadillo/armadillo/work/armadillo-8.200.1/src/wrapper.cpp:51:
:info:build In file included from /opt/local/include/hdf5.h:22:
:info:build /opt/local/include/H5public.h:59:13: fatal error: 'mpi.h' file
not found
:info:build # include <mpi.h>
:info:build ^~~~~~~
:info:build 1 error generated.
}}}
This is on macOS 10.12 with Xcode 9.0, with arpack
@3.4.0_2+accelerate+gcc6 having already been successfully built; it occurs
also on 10.11 with Xcode 8.3.3, and first started in early September.
Annoyingly, it only seems to happen in production builds, and it
consistently fails to fail when attempted on a build which is otherwise
empty.

Please let me know if there's any more information you need, or what other
tests to make. Please see also https://trac.macports.org/ticket/55080,
which started failing the same way at the same time, but which does fail
on an empty build.

--
Ticket URL: <https://trac.macports.org/ticket/55153>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2017-10-23 09:14:57 UTC

Permalink

#55153: armadillo @8.200.1 +arpack: 'mpi.h' file not found
-----------------------------+-------------------
Reporter: majoc-at-astro | Owner:
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.4.2
Resolution: | Keywords:
Port: armadillo |
-----------------------------+-------------------
Changes (by majoc-at-astro):

* Attachment "armadillo.log.2017-10-20_13.21.52" added.

Build log for armadillo +arpack from production

--
Ticket URL: <https://trac.macports.org/ticket/55153>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2017-10-23 11:01:53 UTC

Permalink

MacPorts

2017-10-23 11:04:51 UTC

Permalink

MacPorts

2017-10-23 13:21:48 UTC

Permalink

Post by MacPorts
{{{
:info:build In file included from
:info:build /opt/local/include/H5public.h:59:13: fatal error: 'mpi.h'
file not found
:info:build # include <mpi.h>
:info:build ^~~~~~~
:info:build 1 error generated.
}}}
This is on macOS 10.12 with Xcode 9.0, with arpack
@3.4.0_2+accelerate+gcc6 having already been successfully built; it
occurs also on 10.11 with Xcode 8.3.3, and first started in early
September. Annoyingly, it only seems to happen in production builds, and
it consistently fails to fail when attempted on a build which is
otherwise empty.
Please let me know if there's any more information you need, or what
other tests to make. Please see also
https://trac.macports.org/ticket/55080, which started failing the same
way at the same time, but which does fail on an empty build.

New description:

Log from last Friday's build run to be attached. Here's the top bit:
{{{
:info:build In file included from
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_armadillo/armadillo/work/armadillo-8.200.1/src/wrapper.cpp:51:
:info:build In file included from /opt/local/include/hdf5.h:22:
:info:build /opt/local/include/H5public.h:59:13: fatal error: 'mpi.h' file
not found
:info:build # include <mpi.h>
:info:build ^~~~~~~
:info:build 1 error generated.
}}}
This is on macOS 10.12 with Xcode 9.0, with arpack
@3.4.0_2+accelerate+gcc6 having already been successfully built; it occurs
also on 10.11 with Xcode 8.3.3, and first started in early September.
Annoyingly, it only seems to happen in production builds, and it
consistently fails to fail when attempted on a build which is otherwise
empty.

Please let me know if there's any more information you need, or what other
tests to make. Please see also ticket:55080, which started failing the
same way at the same time, but which does fail on an empty build.

--

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2017-10-23 13:32:13 UTC

Permalink

Post by MacPorts
You are building arpack +mpi. armadillo assumes arpack w/o +mpi.

Not explicitly:
{{{
port install arpack +gcc6
}}}
But now I look, I find openmpi-gcc6 installed further up the build list
for other purposes, though None is selected as gcc at the point arpack is
built. That might explain why I haven't managed to reproduce the problem
in test builds.

Please stand by. That's given me a bunch of things to try.

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2017-10-24 16:16:37 UTC

Permalink

Post by MacPorts
You are building arpack +mpi. armadillo assumes arpack w/o +mpi.

Turns out it's not arpack, but hdf5; and hdf5 +openmpi is used elsewhere
by us in multiple places. Kludging round this will not be trivial. Hm.

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2017-10-25 12:57:07 UTC

Permalink

Post by MacPorts
You are building arpack +mpi. armadillo assumes arpack w/o +mpi.

Turns out it's not arpack, but hdf5 [snip]

My bad: arpack does also take +openmpi, but we don't tell it to
explicitly. How it picks it up, I know not.

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2017-11-01 09:53:39 UTC

Permalink

#55153: armadillo @8.200.1 +arpack: 'mpi.h' file not found
-----------------------------+-------------------------
Reporter: majoc-at-astro | Owner: Schamschula
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.4.2
Resolution: | Keywords:
Port: armadillo |
-----------------------------+-------------------------

Comment (by majoc-at-astro):

I have a partial workaround (of which I'm not proud), with which our build
scripts fail to fail. Once the resulting armadillo has been tested by
real users, I'll report back.

{{{
hdf5_openmpi_variants="`port installed hdf5 | awk '/active/ {print $2}'`"
port -f deactivate hdf5
port install armadillo +arpack # pulls in hdf5 with default variants
port -f deactivate hdf5
port activate hdf5 $hdf5_openmpi_variants
}}}

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2018-11-29 23:33:17 UTC

Permalink

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2018-11-30 01:01:03 UTC

Permalink

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2018-11-30 16:57:42 UTC

Permalink

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2018-12-06 15:01:02 UTC

Permalink

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS

MacPorts

2018-12-06 16:33:26 UTC

Permalink

--
Ticket URL: <https://trac.macports.org/ticket/55153#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS