#1 Disable openmpi and mpich for Flatpak-bundled builds
Merged 5 years ago by jwakely. Opened 5 years ago by otaylor.
rpms/ otaylor/boost flatpak-no-openmpi-mpich  into  master

file modified
+11 -1
@@ -7,6 +7,12 @@ 

  %global boost_docdir __tmp_docdir

  %global boost_examplesdir __tmp_examplesdir

  

+ %if 0%{?flatpak}

+ # For bundling in Flatpak, currently build without mpich and openmpi,

+ # which aren't needed and cause prefix=/app errors.

+ %bcond_with mpich

+ %bcond_with openmpi

+ %else

  # All arches have mpich

  %bcond_without mpich

  
@@ -16,6 +22,7 @@ 

  %else

    %bcond_without openmpi

  %endif

+ %endif

  

  %ifnarch %{ix86} x86_64 %{arm} ppc64 ppc64le aarch64

    %bcond_with context
@@ -36,7 +43,7 @@ 

  Summary: The free peer-reviewed portable C++ source libraries

  Version: 1.66.0

  %global version_enc 1_66_0

- Release: 14%{?dist}

+ Release: 15%{?dist}

  License: Boost and MIT and Python

  

  %global toplev_dirname %{name}_%{version_enc}
@@ -1488,6 +1495,9 @@ 

  %{_mandir}/man1/bjam.1*

  

  %changelog

+ * Thu Sep 27 2018 Owen Taylor <otaylor@redhat.com> - 1.66.0-15

+ - Disable openmpi and mpich for Flatpak-bundled builds

+ 

  * Thu Aug 23 2018 Jonathan Wakely <jwakely@redhat.com> - 1.66.0-14

  - Fix permissions and python shebang of Boost.Build files

  

The Fedora OpenMPI and MPICH Flatpaks pose considerable challenges for
rebuilding to use in Flaptaks with prefix=/app - in particular because
of their use of environment-modules. An analysis of all graphical
applications in Fedora that we might want to create Flatpak containers
of shows no apps that use the OpenMPI and MPICH subpackages of boost,
though many other boost packages are used. So simply disabling openmpi
and mpich for Flatpak rebuilds is the simplest approach.

Pull-Request has been merged by jwakely

5 years ago

Looks like the sensible solution - thanks for the patch.

Would you mind if I merged this back to f29 too?