Re: [O-MPI users] Difficulties building 1.0rc2 on Tiger

2005-10-11 Thread Brian Barrett
On Oct 11, 2005, at 1:10 PM, Charles Williams wrote: I have successfully built several previous releases on my machine, but this last release exited with an error. I am attaching the build and config logs, but as near as I can tell, the problem is a simple typo in the source file. I was a

[O-MPI users] Difficulties building 1.0rc2 on Tiger

2005-10-11 Thread Charles Williams
Hi,I have successfully built several previous releases on my machine, but this last release exited with an error.  I am attaching the build and config logs, but as near as I can tell, the problem is a simple typo in the source file.  I was able to get things to build (although I haven't yet tested

[O-MPI users] RE-make problems

2005-10-11 Thread sdamjad
Brain here is the output of make and make install make.out Description: Binary data makeinstall.out Description: Binary data

Re: [O-MPI users] [Beowulf] MPI ABI

2005-10-11 Thread Toon Knapen
William Gropp wrote: > > Fortran name mangling here means how are Fortran routine names in the > source code mapped to names in the object library. For example, is > > MPI_Init > > in the Fortran source mapped to > > MPI_INIT > mpi_init > mpi_init_ > mpi_init__ > MPI_Init_ > > Each of these h

Re: [O-MPI users] [Beowulf] MPI ABI

2005-10-11 Thread Toon Knapen
Greg Lindahl wrote: >>ignoring the politics for a moment, what are the technical sticking points? > > Fortran name-mangling Up to the MPI 1.2, f77 is used so only functions that are new in MPI2 will be available in a mangled version only. So all others can be linked with using C linkage conventio