Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#39588 closed defect (fixed)

arpack fails to build

Reported by: su1shi4fu3@… Owned by: mamoll (Mark Moll)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc:
Port: arpack

Description (last modified by ryandesign (Ryan Schmidt))

arpack with the variants +openmpi fails to build. (Variants +mpich probably suffers from the same problem, but I could not test this yet.)

The following patch fixes the problem:

--- Portfile.old	2013-06-30 15:54:51.000000000 +0200
+++ Portfile.new	2013-06-30 15:54:35.000000000 +0200
@@ -78,6 +78,7 @@
     configure.args-delete  --disable-mpi
     configure.args-append  --enable-mpi
     configure.env-append   F77=${prefix}/bin/openmpif77
+    configure.env-append   MPIF77=${prefix}/bin/openmpif77
 }
 
 variant mpich description {build PARPACK, with MPICH} conflicts gcc43 gcc44 gcc45 gcc46 gcc47 g95 openmpi {

Change History (4)

comment:2 Changed 5 years ago by ryandesign (Ryan Schmidt)

Cc: mmoll@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to mmoll@…

comment:3 Changed 5 years ago by mamoll (Mark Moll)

Resolution: fixed
Status: newclosed

Fixed in r107476.

comment:4 Changed 5 years ago by dstrubbe (David Strubbe)

Comment: this problem could occur only if you also had some non-macports non-functional mpif77 installed.

comment:5 Changed 5 years ago by su1shi4fu3@…

Yes, I was aware of that. But there are many reasons to have multiple fortran compilers installed, i.e., testing for other packaging systems or pre-release versions.

Note: See TracTickets for help on using tickets.