Re: BIG libraries with self-compiled version

[Michael Creel]

John W. Eaton wrote:

> On 28-Sep-2005, Michael Creel wrote:
>
> | Now I'm intrigued why octave is checking for mpi.h. M.
>
> Because there were some plans a while back to incorporate MPI directly
> in Octave so that the mpi init function could be called first thing as
> some people were claiming was necessary (or specified by the mpi
> standards document).  This seems not to be necessary though, so the
> check could probably be removed from Octave's configure script and
> left to an external MPI package instead.
>
> jwe
>
>  
Perhaps it would be a good idea to incorporate MPITB into Octave. It is 
licensed GPL, and Javier Fernández, the developer, has indicated that he 
wouldn't mind putting it into octave-forge, if he could get help making 
it build using the o-f system. I expect that the same would go for 
direct incorporation into Octave. MPITB just makes mpi functions 
available to Octave. If they're not used, Octave functions as normal - 
there's no need to do MPI_Init at the outset. So its presence shouldn't 
bother anyone, and it could also be built optionally. With dual core 
systems ready to hit the mass market, it would be a shame if Octave were 
to use only half the computing power of such machines.
M.



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------