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 1278066 - [nwchem] make nwchem ExclusiveArch for x86
Summary: [nwchem] make nwchem ExclusiveArch for x86
Alias: None
Product: Fedora
Classification: Fedora
Component: nwchem
Version: rawhide
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: marcindulak
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ZedoraTracker PPCTracker F-ExcludeArch-ppc64le, PPC64LETracker
TreeView+ depends on / blocked
Reported: 2015-11-04 16:09 UTC by Rafael Fonseca
Modified: 2015-12-16 11:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-16 11:00:00 UTC

Attachments (Terms of Use)
intel exclusive patch (deleted)
2015-11-04 16:09 UTC, Rafael Fonseca
no flags Details | Diff

Description Rafael Fonseca 2015-11-04 16:09:43 UTC
Created attachment 1089753 [details]
intel exclusive patch

Description of problem: nwchem depends on openblas-devel which is ExclusiveArch for intel platforms. Currently, the ppc build is disabled only in Epel whereas it should be always disabled. s390 should also be disabled.

Instead of disabling it for any arch except x86, I changed the spec file to make it ExclusiveArch, resulting in a cleaner spec file.

There is also a conditional the doesn't seem to be doing anything in there

%if 0%{?el6}
%global mpich mpich
%global mpich_load %_mpich_load
%global mpich_unload %_mpich_unload
%global mpich mpich
%global mpich_load %_mpich_load
%global mpich_unload %_mpich_unload

so I removed it.

The updated spec file is attached.

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

How reproducible: try to build nwchem on ppc, s390, arm or aarch.

Additional info: patch attached.

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