Is your OMPI installed on an NFS partition? If so, is it in the same mount
point on all nodes?
Most likely problem is that the required libraries were not found on the remote
node
> On Feb 8, 2016, at 10:45 AM, Rahul Pisharody wrote:
>
> Hello all,
>
> I'm trying to get a simple program (pr
Hello all,
I'm trying to get a simple program (print the hostname of the executing
machine) compiled with openmpi run across multiple machines on Univa Grid
Engine.
This particular configuration has many of the ports blocked. My run command
has the mca options necessary to limit the ports to the
Awesome; thanks Gilles.
> On Feb 8, 2016, at 9:29 AM, Gilles Gouaillardet
> wrote:
>
> ok, will do
>
> Cheers,
>
> Gilles
>
> On Monday, February 8, 2016, Jeff Squyres (jsquyres)
> wrote:
> I like your suggestion better -- if we can somehow report during the
> compile/link that the reaso
ok, will do
Cheers,
Gilles
On Monday, February 8, 2016, Jeff Squyres (jsquyres)
wrote:
> I like your suggestion better -- if we can somehow report during the
> compile/link that the reason for the error is because Open MPI was not
> compiled with Fortran support, that would definitely be prefe
On Feb 8, 2016, at 8:59 AM, Brian Taylor wrote:
> I want a program that's using Fortran MPI types to **FAIL** when built
> against an MPI library that doesn't support Fortran, preferably at compile
> time, with a very loud "NO FORTRAN SUPPORT!!!" error message. I don't
> expect, nor want, any
I like your suggestion better -- if we can somehow report during the
compile/link that the reason for the error is because Open MPI was not compiled
with Fortran support, that would definitely be preferable.
FWIW: my suggestion was because I wanted to convey the *reason* for the error
(i.e., th
On Mon, Feb 8, 2016 at 12:31 AM, Jeff Hammond
wrote:
>
>> > BTW: is there a reason you don't want to just use the C datatypes? The
>> fundamental output of the index is an integer value -- casting it to a
>> float of some flavor doesn't fundamentally change its value.
>>
>> The code in question
Waiting until runtime to issue this error is a terrible idea, because then
the PETSc team (among others) will disparage you for allowing a user to
successfully build against an unusable library. They are on-record
numerous times in the past as to the evils of e.g. no-op symbols in MPI or
other run
The issue at hand is trying to help the user figure out that they have an open
MPI built without fortran support.
Perhaps we should improve the error reporting at run time to display something
about the fact that you used a fortran data type but have an OMPI that was
compiled without fortran su
That being said, should we remove these fortran types from include files and
libs when ompi is configure'd without fortran support ?
Cheers,
Gilles
Jeff Hammond wrote:
>
>> BTW: is there a reason you don't want to just use the C datatypes? The
>> fundamental output of the index is an integer
>
>
> > BTW: is there a reason you don't want to just use the C datatypes? The
> fundamental output of the index is an integer value -- casting it to a
> float of some flavor doesn't fundamentally change its value.
>
> The code in question is not mine. I have suggested to the developers that
> th
11 matches
Mail list logo
