On 27 November 2017 at 17:55, Allin Cottrell wrote:
| On Sun, 26 Nov 2017, Dirk Eddelbuettel wrote:
|
| > On 26 November 2017 at 18:40, Allin Cottrell wrote:
| > | On Sat, 25 Nov 2017, Dirk Eddelbuettel wrote:
| > |
| > | > No luck so far. I added the (virtual) packages mpi-default-dev and
| > | > mpi-default-bin (mostly OpenMPI, but some of Debian arches may use MPICH).
| > | > They are installed but your configure then report
| > | >
| > | > checking for mpicc... yes
| > | > checking for MPI library... Couldn't find MPI library
| > | >
| > | > Hence:
| > | >
| > | > Configuration:
| > | >
| > | > Installation path: /usr
| > | > Use readline library: yes
| > | > Use gnuplot for graphs: yes
| > | > Use pdflatex for typesetting: yes
| > | > Use libgsf for zip/unzip: no
| > | > sse2 support for RNG: no
| > | > OpenMP support: yes
| > | > MPI support: no
| > | [...]
| > | >
| > | > Could you[r] configure possibly rely on this:
| > | >
| > | > edd@brad:~$ pkg-config --cflags mpi
| > | > -pthread -I/usr/lib/x86_64-linux-gnu/openmpi/include
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi
| > | > edd@brad:~$ pkg-config --libs mpi
| > | > -L/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr//lib -lmpi
| > | > edd@brad:~$
| > |
| > | Hmm, maybe, but I think Debian is unusual in supplying an mpi.pc
| > | file (not present on Fedora or Arch anyway).
| > |
| > | Could you try using the config variable(s) --with-mpi-lib= (and
| > | perhaps also --with-mpi-include=)?
| >
| > Not easily. See how those values have x86_64 in them? We have
| > over 10 different architectures (even if x86_64 may cover 98% of
| > users) and my build recipe is supposed to cover all equally.
|
| OK, understood. Please try the attached patch for the configure
| script in gretl-2017d.
Nice work, and I really appreciate it. Seems to work too:
OpenMP support: yes
MPI support: yes
Build in progress so I better not jinx it ...
| I'm keeping Jack in cc in case he has time to experiment, in an
| attempt to avoid the case where we support a multi-arch build
| environment at the cost of breaking a single-arch one.
Sure. Earlier you wrote
On 27 November 2017 at 11:25, Allin Cottrell wrote:
| On Mon, 27 Nov 2017, Riccardo (Jack) Lucchetti wrote:
|
| > On Sun, 26 Nov 2017, Allin Cottrell wrote:
| >
| >>> No luck so far. I added the (virtual) packages mpi-default-dev and
| >>> mpi-default-bin (mostly OpenMPI, but some of Debian arches may use MPICH).
| >>> They are installed but your configure then report
| >
| > I have no problems here with libopenmpi-dev.
|
| Good to hear, but I think in Dirk's case he's (cross-) building gretl
| for several architectures on a given server, which adds a layer of
| complication.
Not really. I build on my platform, and then ship my sources. Autobuilders
pick those up and build on theirs. So I am lower-tech -- no magic
multiplatform builders here.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | edd(a)debian.org