Re: [O-MPI devel] ltdl.h problem

2005-08-31 Thread George Bosilca
Now I see the reason behind this change. Anyway, few month ago we decide to switch the compilation process, and to modify all the files in order to start all the #include directives with the full path of the include files (starting the main components top directories). Personally, I prefer to keep

Re: [O-MPI devel] ltdl.h problem

2005-08-31 Thread Ralf Wildenhues
* George Bosilca wrote on Thu, Sep 01, 2005 at 06:27:27AM CEST: > I trace this one as far as I could. And the results are mostly unexpected. > On some of the clusters it compiles without any problems and on some > others it doesn't. The difference is ... if there is an ltdl.h installed > in the sys

Re: [O-MPI devel] ltdl.h problem

2005-08-31 Thread George Bosilca
I trace this one as far as I could. And the results are mostly unexpected. On some of the clusters it compiles without any problems and on some others it doesn't. The difference is ... if there is an ltdl.h installed in the system directories. I don't think that's the expected behavior for the comp

Re: [O-MPI devel] ltdl.h problem

2005-08-31 Thread Ralf Wildenhues
Hi George, * George Bosilca wrote on Thu, Sep 01, 2005 at 05:54:15AM CEST: > Starting from yesterday I'm unable to compile on several clusters. I check > the version of libtool, automake and autoconf and they all are the latest. > However, in all the component I get similar errors: > > In file in

[O-MPI devel] ltdl.h problem

2005-08-31 Thread George Bosilca
Starting from yesterday I'm unable to compile on several clusters. I check the version of libtool, automake and autoconf and they all are the latest. However, in all the component I get similar errors: In file included from ../../../../../ompi-trunk/opal/mca/maffinity/base/maffinity_base_close.c:2

Re: [O-MPI devel] pml vs bml vs btl

2005-08-31 Thread Galen M. Shipman
On Aug 31, 2005, at 1:06 PM, Jeff Squyres wrote: On Aug 29, 2005, at 9:17 PM, Brad Penoff wrote: PML: Pretty much the same as it was described in the paper. Its interface is basically MPI semantics (i.e., it sits right under MPI_SEND and the rest). BTL: Byte Transfer Layer; it's the next g

Re: [O-MPI devel] pml vs bml vs btl

2005-08-31 Thread Jeff Squyres
On Aug 29, 2005, at 9:17 PM, Brad Penoff wrote: PML: Pretty much the same as it was described in the paper. Its interface is basically MPI semantics (i.e., it sits right under MPI_SEND and the rest). BTL: Byte Transfer Layer; it's the next generation of PTL. The BTL is much more simple tha

Re: [O-MPI devel] Small ltdl use update

2005-08-31 Thread Ralf Wildenhues
Hi Jeff, * Jeff Squyres wrote on Wed, Aug 31, 2005 at 12:58:05PM CEST: > On Aug 31, 2005, at 2:48 AM, Ralf Wildenhues wrote: > > > Please apply the first patch (or a similar solution) to include > > ltdl.h directly. This is both how it's documented and how > > it will work with Libtool 1.5.x and

[O-MPI devel] "fix" for romio configure.in

2005-08-31 Thread Ralf Wildenhues
This is a rather subtle issue, and pretty ugly, unfortunately. For the curious reader, here is a rather technical explanation: Somewhere, inside some if test "$arch_..." branching construct (but not inside an Autoconf macro definition!), the configure.in script uses the macro AC_CHECK_HEADER. T

Re: [O-MPI devel] Small ltdl use update

2005-08-31 Thread Jeff Squyres
On Aug 31, 2005, at 2:48 AM, Ralf Wildenhues wrote: Please apply the first patch (or a similar solution) to include ltdl.h directly. This is both how it's documented and how it will work with Libtool 1.5.x and 2.x: the latter has other included files, which live one directory level further down

[O-MPI devel] Small ltdl use update

2005-08-31 Thread Ralf Wildenhues
Please apply the first patch (or a similar solution) to include ltdl.h directly. This is both how it's documented and how it will work with Libtool 1.5.x and 2.x: the latter has other included files, which live one directory level further down. Below is another tiny patch to please "make distche