> On Oct 22, 2018, at 12:58 PM, Santiago Serebrinsky
> wrote:
>
> Precisely, that was the problem.
>
> I disabled Fortran support to move ahead and see if I could manage that way
> (and I found I couldn't!), at least in some of my uses. But I (and perhaps
> others as well) would still need
Precisely, that was the problem.
I disabled Fortran support to move ahead and see if I could manage that way
(and I found I couldn't!), at least in some of my uses. But I (and perhaps
others as well) would still need to have Fortran support, so the issue is
not moot at all.
Thanks
On Mon, Oct
For what it's worth, it looks like Open MPI's configure found your mingw
fortran compiler, but was unable to determine what flag to use to find fortran
modules -- that's what caused configure to abort.
From your later messages, it looks like you just ended up disabling Fortran
support, so this
Compiler:
$ which gfortran.exe
/mingw64/bin/gfortran.exe
I am attaching config.log (renamed to keep track of the error produced).
PS: To try moving further, I did
./configure --prefix=$HOME/usr/local --disable-mpi-fortran
which led me to a later error. This is posted in a separate thread.
Also, please send the entire output from configure as well as the config.log
file (please compress).
Thanks!
> On Oct 21, 2018, at 4:08 AM, Marco Atzeri wrote:
>
> Am 21.10.2018 um 09:56 schrieb Santiago Serebrinsky:
>> Hi all,
>> I am using Msys2 from PortableApps under Win10. More
Am 21.10.2018 um 09:56 schrieb Santiago Serebrinsky:
Hi all,
I am using Msys2 from PortableApps under Win10. More precisely,
|$ uname -a MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 13:25
i686 Msys |
I mean to install openmpi. Since I found no pre-built package (I would
love to
Hi all,
I am using Msys2 from PortableApps under Win10. More precisely,
$ uname -a
MSYS_NT-10.0-WOW Galapagos 2.11.1(0.329/5/3) 2018-09-10 13:25 i686 Msys
I mean to install openmpi. Since I found no pre-built package (I would love
to have it!), I downloaded openmpi-3.1.2. When I
