Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1518038

Summary: fftw FTBFS on f27 and rawhide
Product: [Fedora] Fedora Reporter: Merlin Mathesius <mmathesi>
Component: fftwAssignee: Conrad Meyer <cse.cem+redhatbugz>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: cse.cem+redhatbugz, rdieter, susi.lehtola, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: fftw-3.3.5-8.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-24 04:02:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Merlin Mathesius 2017-11-28 00:35:44 UTC
Description of problem:
fftw no longer builds on Fedora F27 or Rawhide. The last successful package build was on August 4, 2017 for F27. There does not appear have been any build attempts for Rawhide.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. fedpkg clone fftw
2. cd fftw
3. fedpkg scratch-build
4. fedpkg --release f27 scratch-build

Actual results:
Failed Rawhide scratch build:
Failed F27 scratch build:

Expected results:
Successful package build

Additional info:
Package still builds successfully for F26:

I have attempted to rebuild the fftw package numerous times. It is always the build for arch i686 that fails, and it is always the self-checks that fail with a segfault or a hang. I have also observed that the failing self-checks are always those using Open MPI in a multi-CPU configuration.

Note: the segfault traceback appears similar to that reported at so the failure may be associated with the openmpi package.

Comment 1 Rex Dieter 2017-11-28 16:48:13 UTC
I believe i686 is not longer treated as a primary arch, it may not be unreasonable to either skip tests or make the tests non-fatal on that architecture.

Comment 2 Merlin Mathesius 2017-11-28 22:25:42 UTC
Yes, according to, as of Fedora 26 i686 has been demoted to an alternative architecture.


After further investigation, it appears the problem can be worked around by disabling Open MPI's vader byte transfer layer while running self-checks on 32-bit x86 platforms by setting OMPI_MCA_btl="^vader" in the environment. Assuming my scratch builds with that workaround finish successfully, I'll be creating a PR with that patch in the very near future.

Comment 3 Merlin Mathesius 2017-11-29 16:09:51 UTC
I have created PRs with fixes for this issue:



Comment 4 Merlin Mathesius 2017-12-13 16:51:14 UTC
Please consider merging the above referenced PRs--or implementing an alternate fix--so that fftw can build successfully again.

Comment 5 Conrad Meyer 2018-04-19 02:12:16 UTC
Rawhide fix from comment #3 was already merged; merged F27 fix as well and kicked off a build:

Comment 6 Conrad Meyer 2018-04-19 02:14:09 UTC
FYI this may have been fixed in OpenMP already:  It's unclear to me what release version(s) that ended up in.  Nevertheless, disabling the check on x86 seems harmless.

Comment 7 Fedora Update System 2018-04-19 04:16:38 UTC
fftw-3.3.5-8.fc27 has been submitted as an update to Fedora 27.

Comment 8 Fedora Update System 2018-04-19 17:38:28 UTC
fftw-3.3.5-8.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See for
instructions on how to install test updates.
You can provide feedback for this update here:

Comment 9 Fedora Update System 2018-04-24 04:02:04 UTC
fftw-3.3.5-8.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.