George Bosilca at U. Tennessee is working on a native Windows port
for Open MPI; I don't know if anyone has ever tried to compile or run
it under cygwin.
George -- can you comment?
On Feb 27, 2007, at 10:00 PM, Ganapathi Kamath wrote:
Justing passing along some information about
Hi everybody,
first I'd like to introduce myself, my name is Götz Waschk and I'm
working at DESY in the computing department.
The default shell here is /bin/zsh. mpirun has support for setting
PATH and LD_LIBRARY_PATH for a list of known shells (bash, ksh, csh,
...) but not for zsh.
This patch
Actually, I have also tried with the same version you are using and
cannot reproduce the behavior. Can you get a backtrace from the
segmentation fault?
Also, as Ralph suggested, you might want to upgrade and see if the
problem persists.
Tim
On Mar 1, 2007, at 8:52 AM, Ralph Castain
Few months ago it was compiling nicely under Cygwin, Mingw and
Interix. They are definitively very Unix like environments so few
changes were required. All changes I made are now in the trunk, so I
expect a smooth compilation under all these environments. I used 2
compilers, the mingw gcc
That's awesome. Good work :)
-- Josh
On Mar 1, 2007, at 11:59 AM, Ethan Mallove wrote:
Folks,
If some of you hadn't already noticed, reports (see
http://www.open-mpi.org/mtt/) on Test Runs have been taking
an upwards of 5-7 minutes to load as of late. This was due
in part to some database
I just added a client/mtt-submit script to the mtt/trunk SVN
repository which will help you. You'll need to use it like
this:
$ client/mtt-submit -f '/directory/where/results/are/*.txt' -g -u cisco -p
/directory/where/results/are/ is specified in your INI file
as mttdatabase_debug_filename.
On Mar 1, 2007, at 2:03 PM, Ethan Mallove wrote:
Good point. If the mtt client couldn't contact the
database, then Test Builds and Test Runs will not contain
their required mpi_install and test_build ID's (you'll see
FOREIGN KEY constraint errors in the output).
Not being able to contact the
