Heh. The list overrides the reply-to. :-)
Agreed -- let's you, me, and Brian discuss off-list and let anyone who
cares know what the final solution is that we come up with.
FWIW, we've become quite fond of developing in mercurial branches and
pushing them somewhere to share when you want
On Jul 22, 2009, at 10:55 AM, Brian W. Barrett wrote:
The current autodetect implementation seems like the wrong approach
to me. I'm rather unhappy the base functionality was hacked up like
it was without any advanced notice or questions about original
design intent. We seem to have a set
The current autodetect implementation seems like the wrong approach to me.
I'm rather unhappy the base functionality was hacked up like it was
without any advanced notice or questions about original design intent.
We seem to have a set of base functions which are now more unreadable than
before
On Jul 21, 2009, at 8:01 PM, Iain Bason wrote:
> $ mpicc -g -Isrc -c -o libmpitest.o libmpitest.c
> Cannot open configuration file ${datadir}/openmpi/mpicc-wrapper-
> data.txt
> Error parsing data file mpicc: Not found
Is this just mpicc, or is it also ompi_info and mpirun failing like
this?
On Jul 21, 2009, at 7:48 PM, Jeff Squyres wrote:
Arrgh!! Even with .ompi_ignore, everything is broken on OS X and
Linux (perhaps this is what Ralph was referring to -- not a compile
time problem?):
-
$ mpicc -g -Isrc -c -o libmpitest.o libmpitest.c
Cannot open configuration file ${d
On Jul 21, 2009, at 7:55 PM, Iain Bason wrote:
> $ ./configure --prefix=/home/jsquyres/bogus --disable-mpi-f77 --
> enable-mpirun-prefix-by-default
>
> No OPAL_* env variables set.
>
> Same thing happens on OS X and Linux.
And does it fail when actually installed in /home/jsquyres/bogus, or
on
On Jul 21, 2009, at 7:50 PM, Jeff Squyres wrote:
On Jul 21, 2009, at 7:46 PM, Iain Bason wrote:
> The help file should have been found. This is on Linux RHEL4,
but I
> doubt it's a Linux-version-specific issue...
Could you send me your configure options, and your OPAL_XXX
environment vari
On Jul 21, 2009, at 7:50 PM, Jeff Squyres wrote:
If you have an immediate fix for this, that would be great --
otherwise, please back this commit out (I said in my previous mail
that I would back it out, but I had assumed that you were gone for
the day. If you're around, please make the c
On Jul 21, 2009, at 7:46 PM, Iain Bason wrote:
> The help file should have been found. This is on Linux RHEL4, but I
> doubt it's a Linux-version-specific issue...
Could you send me your configure options, and your OPAL_XXX
environment variables?
$ ./configure --prefix=/home/jsquyres/bog
Arrgh!! Even with .ompi_ignore, everything is broken on OS X and
Linux (perhaps this is what Ralph was referring to -- not a compile
time problem?):
-
$ mpicc -g -Isrc -c -o libmpitest.o libmpitest.c
Cannot open configuration file ${datadir}/openmpi/mpicc-wrapper-data.txt
Error parsing
On Jul 21, 2009, at 6:34 PM, Jeff Squyres wrote:
Also, it seems broken:
[15:31] svbu-mpi:~/svn/ompi4 % ompi_info | grep installd
--
Sorry! You were supposed to get help about:
developer warning: field too long
But I co
On Jul 21, 2009, at 6:34 PM, Jeff Squyres wrote:
I'm quite confused about what this component did to the base
functions. I haven't had a chance to digest it properly, but it
"feels wrong"... Iain -- can you please explain the workings of
this component and its interactions with the base?
I'm quite confused about what this component did to the base
functions. I haven't had a chance to digest it properly, but it
"feels wrong"... Iain -- can you please explain the workings of this
component and its interactions with the base?
Also, it seems broken:
[15:31] svbu-mpi:~/svn/om
13 matches
Mail list logo
