From: Ralf Wildenhues <ralf.wildenh...@gmx.de>
Date: August 4, 2008 2:53:49 PM EDT
To: Jeff Squyres <jsquy...@cisco.com>
Cc: Open MPI Users <us...@open-mpi.org>
Subject: Re: [OMPI users] Problems building openmpi 1.2.6 with Lahey
Fortran
Hello Craig, Jeff,
* Jeff Squyres wrote on Sun, Aug 03, 2008 at 03:20:17PM CEST:
Open MPI uses GNU Libtool to build itself. I suspect that perhaps
Libtool doesn't know the Right Mojo to understand the Lahey compilers,
and that's why you're seeing this issue. As such, it might well be that
your workaround is the best one.
Ralf -- we build the OMPI 1.2 series with that same "late beta" Libtool
(2.1a) that we have forever. Do you recall offhand if Libtool 2.x
before
2.2 supported the Lahey fortran compilers?
Libtool does not yet support Lahey. Neither Absoft Fortran 90
(which was asked about a while ago).
If you would like to see support for Lahey and Absoft in Libtool,
here's what you can do that really helps getting there faster:
- get me some access to these compilers. A login to a system
with one of them would be great, but a long-term trial version
(2 weeks helps little for later regression testing) would be
better than nothing, too (sometimes a friendly email is all it
takes for this);
- alternatively, a volunteer that has access to the compilers,
to help me with the port, or do the porting herself. This will
require installing git Libtool and running its testsuite anywhere
between once and several times, and reading and sending some emails
with patches resp. test results.
Otherwise, here's some tips for workaround building: edit the generated
libtool scripts (there are a few in the OpenMPI build tree) and set
pic_flag (to --shared), archive_cmds (to contain --shared), and
archive_export_cmds correctly everywhere. These variables are set once
for each compiler: the C compiler comes at the beginning, all other ones
near the end of the script.
Cheers,
Ralf
