Bug 193857 - Lam does not include trillium support due to a typo on the configure call.
Summary: Lam does not include trillium support due to a typo on the configure call.
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lam   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Doug Ledford
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-06-02 09:55 UTC by Jose Plans
Modified: 2018-10-19 20:39 UTC (History)
2 users (show)

Fixed In Version: RHEA-2007-0299
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-01 17:28:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
SPEC fix. (675 bytes, patch)
2006-06-02 09:55 UTC, Jose Plans
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2007:0299 normal SHIPPED_LIVE OpenIB Infiniband enhancement update 2007-05-01 17:28:47 UTC

Description Jose Plans 2006-06-02 09:55:38 UTC
 RHEL4's LAM package does not include the support for Trillium due to a typo on
its SPEC file, instead of calling --with-trillium, we call --enable-trillium
which invalidates the addition of the feature.
 This prevents the customer to build his own XMPI application 
  (see http://www.lam-mpi.org/softwar e/xmpi/)
 Attached you will find the patch fixing the original SPEC file,

Comment 1 Jose Plans 2006-06-02 09:55:39 UTC
Created attachment 130392 [details]
SPEC fix.

Comment 2 Jason Vas Dias 2006-06-06 00:39:11 UTC
This is now fixed with lam-7.0.6-6, available from:
and queued for release in a RHEL-4 update .

Comment 12 Red Hat Bugzilla 2007-05-01 17:28:50 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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