Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 589641 - mvapich-1.2.0-0.3562.1.el5.src.rpm does not have Fortran support
mvapich-1.2.0-0.3562.1.el5.src.rpm does not have Fortran support
Status: CLOSED DUPLICATE of bug 584218
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mvapich (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Jay Fenlason
Red Hat Kernel QE team
Depends On:
  Show dependency treegraph
Reported: 2010-05-06 11:33 EDT by Petr Lautrbach
Modified: 2014-08-31 19:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-02-09 12:09:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Petr Lautrbach 2010-05-06 11:33:02 EDT
This is originated on message from Platform preparing RH HPC 5.5:

We have found that the mvapich rpm (mvapich-1.2.0-0.3562.1.el5.src.rpm )
in RHEL 5.5 does not have Fortran support. We require fortran support to
be present for this package in order for us to compile fortran packages
against it.

My observation:
Configure is already run with --enable-f77 --enable-f90
./configure --enable-sharedlib --with-device=ch_gen2 --with-arch=LINUX -prefix=/usr/lib/mvapich/1.2.0-gcc --with-echo --enable-f77 --enable-f90 --with-romio '-lib=-libverbs -libumad -lpthread -Wall' -mpe_opts=--with-cflags=-m32 --with-fflags=-m32

but fortran seems to be disabled during "Configuring Fortran subsystem":
configure: warning: Could not find a way to access the command line from Fortran 77
configure: error: Command line access is required for MPICH
Error configuring the Fortran subsystem!
Turning off Fortran support
Comment 1 Jay Fenlason 2011-02-09 12:09:14 EST

*** This bug has been marked as a duplicate of bug 584218 ***

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