On 26 September 2007 at 13:37, Francesco Pietra wrote:
| Are any detailed directions for upgrading (for common guys, not experts, I
| mean)? My 1.2.3 version on Debian Linux amd64 runs perfectly.
How about
sudo apt-get update; sudo apt-get dist-upgrade
provided you point to Debian unsta
Mostyn,
It looks like the documentation is wrong (and has been wrong for years).
I assume you were looking at the FAQ? I will update it tonight or tomorrow.
Thanks for the report!
Tim
Mostyn Lewis wrote:
I see docs for this like:
--enable-mca-no-build=btl:mvapi,btl:openib,btl:gm,btl:mx,mtl
Today's SVN.
A generated configure has this in it:
...
###
# Libtool: part two
# (after C compiler setup)
ompi_show_subtitle "Libtool configuratio
I see docs for this like:
--enable-mca-no-build=btl:mvapi,btl:openib,btl:gm,btl:mx,mtl:psm
however, the code in a generated configure that parse this looks like:
...
ifs_save="$IFS"
IFS="${IFS}$PATH_SEPARATOR,"
msg=
for item in $enable_mca_no_build; do
Murat,
Thanks for the bug report. I have fixed (slightly differently than you
suggested) this in the Open MPI trunk in r16265 and it should be
available in the nightly trunk tarball tonight.
I will ask to have this moved into the next release of Open MPI.
Thanks,
Tim
Murat Knecht wrote:
C
Hi Teng,
Teng Lin wrote:
Hi,
We would like to distribute OpenMPI along with our software to
customers, is there any legal issue we need to know about?
Not that I know of (disclaimer: IANAL). Open MPI is licensed under the
new BSD license. Open MPI's license is here:
http://www.open-mpi.or
Note that you may be able to get some more error output by
adding --debug-daemons to the mpirun command line.
Tim
On Thursday 27 September 2007 05:12:53 pm Dino Rossegger wrote:
> Hi Jody,
>
> Thanks for your help, it really is the case that either in PATH nor in
> LD_LIBRARY_PATH the path to th
Hi Jody,
Thanks for your help, it really is the case that either in PATH nor in
LD_LIBRARY_PATH the path to the libs is set correctly. I'll try out,
hope it works.
jody schrieb:
> Hi Dino
>
> Try
> ssh saturn printenv | grep PATH
>>from your host sun to see what your environment variables are w
Here's some more info on the problem I've been struggling with; my
apologies for the lengthy posts, but I'm a little desperate here :-)
I was able to reduce the size of the experiment that reproduces the
problem, both in terms of input data size and the number of slots in
the cluster. The clus
On Thu, 2007-09-27 at 14:18 -0400, Tim Prins wrote:
> Åke Sandgren wrote:
> > On Thu, 2007-09-27 at 09:09 -0400, Tim Prins wrote:
> >> Hi Ake,
> >>
> >> Looking at the svn logs it looks like you reported the problems with
> >> these checks quite a while ago and we fixed them (in r13773
> >> https
Åke Sandgren wrote:
On Thu, 2007-09-27 at 09:09 -0400, Tim Prins wrote:
Hi Ake,
Looking at the svn logs it looks like you reported the problems with
these checks quite a while ago and we fixed them (in r13773
https://svn.open-mpi.org/trac/ompi/changeset/13773), but we never moved
them to the
Copy-and-paste-error: The second part of the fix ought to be:
if ( !have_wdir ) {
free(cwd);
}
Murat
Murat Knecht schrieb:
> Hi all,
>
> I think, I found a bug and a fix for it.
> Could someone verify the rationale behind this bug, as I have this
> SIGSEG on only one
Hi all,
I think, I found a bug and a fix for it.
Could someone verify the rationale behind this bug, as I have this
SIGSEG on only one of two machines, and I don't quite see why it doesn't
occur always. (Same testprogram, equally compiled 1.2.4 OpenMPI).
Though the fix does prevent the segmentatio
Hi Dino
Try
ssh saturn printenv | grep PATH
from your host sun to see what your environment variables are when
ssh is run without a shell.
On 9/27/07, Dino Rossegger wrote:
> Hi,
>
> I have a problem running a simple programm mpihello.cpp.
>
> Here is a excerp of the error and the command
> ro
Hi,
I have a problem running a simple programm mpihello.cpp.
Here is a excerp of the error and the command
root@sun:~# mpirun -H sun,saturn main
[sun:25213] [0,0,0] ORTE_ERROR_LOG: Timeout in file
base/pls_base_orted_cmds.c at line 275
[sun:25213] [0,0,0] ORTE_ERROR_LOG: Timeout in file pls_rsh_m
Hi,
We would like to distribute OpenMPI along with our software to
customers, is there any legal issue we need to know about?
We can successfully build OpenMPI using
./configure --prefix=/some_path;make;make install
However, if we do
cp -r /some_path /other_path
and try to run
/other_pat
On Thu, 2007-09-27 at 09:09 -0400, Tim Prins wrote:
> Hi Ake,
>
> Looking at the svn logs it looks like you reported the problems with
> these checks quite a while ago and we fixed them (in r13773
> https://svn.open-mpi.org/trac/ompi/changeset/13773), but we never moved
> them to the 1.2 branch
Hi Ake,
Looking at the svn logs it looks like you reported the problems with
these checks quite a while ago and we fixed them (in r13773
https://svn.open-mpi.org/trac/ompi/changeset/13773), but we never moved
them to the 1.2 branch.
I will ask for this to be moved to the 1.2 branch.
However
We have a working version of Open MPI on Windows. However, it's
manually build and the whole compilation process as well as
maintaining the project file is a nightmare. That's why the Windows
project files are not committed into the trunk.
If you want I can provide you the solution and proj
Hi!
There are a couple of bugs in the configure scripts regarding threads
checking.
In ompi_check_pthread_pids.m4 the actual code for testing is wrong and
is also missing a CFLAG save/add-THREAD_CFLAGS/restore resulting in the
linking always failing for the -pthread test with gcc.
config.log look
20 matches
Mail list logo
