Bug 1204413 - Patch for adding support for openmpi and mpich
Summary: Patch for adding support for openmpi and mpich
Alias: None
Product: Fedora
Classification: Fedora
Component: fftw2
Version: 25
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: José Matos
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-21 19:56 UTC by Mark Harfouche
Modified: 2017-12-12 10:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-12-12 10:10:07 UTC
Type: Bug

Attachments (Terms of Use)
Diff for adding support for mpi in the fftw2 library (4.66 KB, patch)
2015-03-21 19:56 UTC, Mark Harfouche
no flags Details | Diff

Description Mark Harfouche 2015-03-21 19:56:51 UTC
Created attachment 1004935 [details]
Diff for adding support for mpi in the fftw2 library


I went through the hdf5 spec file and adapted it to FFTW2 so that FFTW2 is now compiled with openmpi and mpich.

I don't have a good way to test if this works on other architectures.

Let me know what you think.


Comment 1 Mark Harfouche 2015-03-21 21:02:24 UTC
Also, if anybody cares, the packages are available here


Comment 2 Jan Kurik 2015-07-15 14:22:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 3 Mark Harfouche 2015-08-15 18:49:45 UTC
I disagree with setting this to F23.

The is a bug against the .spec file which is shared among all builds.

This bug is easy to zap. I've even included the patch, and a link to a working repo showing that it does in fact build.

FYI: the link for more information is dead...

Comment 4 Jan Kurik 2016-02-24 13:22:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:

Comment 5 Mark Harfouche 2016-12-12 21:42:52 UTC
reviving this bug because I think the old patch was good enough to publish.

Does anybody want to merge this in?

Comment 6 Fedora End Of Life 2017-11-16 18:53:30 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2017-12-12 10:10:07 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.