On Mon, 28 Nov 2016, Johannes Lips wrote:
On 28.11.2016 10:09, Johannes Lips wrote:
>
>
> On 27.11.2016 08:24, Johannes Lips wrote:
>> On 26/11/16 16:15, Allin Cottrell wrote:
>>> On Sat, 26 Nov 2016, Johannes Lips wrote:
>>>
>>>> Hi all,
>>>>
>>>> since the new release is out, I am trying to compile gretl with the
>>>> additional MPI support. I added the configure option --with-mpi and
>>>> the additional build requirement openmpi-devel, which should include
>>>> the mpicc compiler in /usr/lib/bin, but it's not found by the
>>>> configure script, please see the build logs. [1]
>>>> It would be great if anyone could check what might be wrong.
>>>
>>> Thanks for trying this, Johannes.
>>>
>>> I routinely build gretl with MPI support on Fedora 23. I have the
>>> openmpi.x86_64 and openmpi-devel.x86_64 packages installed (version
>>> 1.8.8-5.fc23.2). These packages place mpicc in
>>> /usr/lib64/openmpi/bin/mpicc and the libraries in
>>> /usr/lib64/openmpi/lib. In addition I have
>>>
>>> module load mpi/openmpi-x86_64
>>>
>>> in my ~/.bash_profile. Under these conditions everything "just
works." I
>>> don't need to give "--with-mpi" when running the
>>> configure script, it's detected and used automatically.
>>>
>>> Allin
>> I've managed to build it properly and the updates will go out shortly.
> Well, that was too early. I am able to build it on 64bit, but 32bit still
> fails. I've asked on the devel mailing list of fedora. [1]
>
> Johannes
Ok, problem found. It seems, that the configure script does not
check the complete library path in the 32bit case. Please see the
thread on fedora-devel for details. Not sure if this is a general
problem in the configure script or rather specific to fedora.
I've now added /usr/lib/openmpi/lib to the default MPI library
search path in gretl's configure script (in git, that is).
When configuring the 2016d release source it's possible to use
--with-mpi-lib=<path> to help things along.
Allin Cottrell