On Jan 25, 2010, at 5:38 PM, Gus Correa wrote:
> A) Keep the FAQ, please!
No worries -- I am not asking about removing the FAQ. I was more asking if
people wanted the *form* of the FAQ would be useful in a different form.
> B) Add an "ALL FAQ" category, to make keyword search easier
> on web b
Hi All,
I am trying to use MPI for scientific High Performance (hpc)
applications. I use MPI_Spawn to create child processes. Is there a way
to start child processes early than the parent process, using MPI_Spawn?
I want this because, my experiments showed that the time to spawn the
children
Hi Jeff
Thanks for your "RFC on FAQs"!
There go my two cents:
A) Keep the FAQ, please!
I am a big fan of the OpenMPI FAQ.
I use them all the time.
I also recommend them to everybody on this list and on other lists.
I've seen a lot of people do the same.
In the absence of more comprehensive doc
On Mon, 25 Jan 2010 15:10:12 -0500, Jeff Squyres wrote:
> Indeed. Our wrapper compilers currently explicitly list all 3
> libraries (-lmpi -lopen-rte -lopen-pal) because we don't know if those
> libraries will be static or shared at link time.
I am suggesting that it is unavoidable for the perso
Actually, let me roll that back a bit. I was preparing a custom patch
for the v1.4 series, and it seems that the code does not have the bug
I mentioned. It is only the v1.5 and trunk that were effected by this.
The v1.4 series should be fine.
I will still ask that the error message fix be b
So while working on the error message, I noticed that the global
coordinator was using the wrong path to investigate the checkpoint
metadata. This particular section of code is not often used (which is
probably why I could not reproduce). I just committed a fix to the
Open MPI development t
On Jan 25, 2010, at 11:58 AM, Mathieu Gontier wrote:
> I built OpenMPI-1.4.1 without openib support with the following configuration
> options:
>
> ./configure
> --prefix=/develop/libs/OpenMPI/openmpi-1.4.1/LINUX_GCC_4_1_tcp_mach
> --enable-static --enable-shared --enable-cxx-exceptions --enab
1 - Do you have problems with openmpi 1.4 too? (I don't, haven't built
1.4.1 yet)
2 - There is a bug in the pathscale compiler with -fPIC and -g that
generates incorrect dwarf2 data so debuggers get really confused and
will have BIG problems debugging the code. I'm chasing them to get a
fix...
3 -
On Jan 25, 2010, at 12:55 PM, Jed Brown wrote:
> > The short version is that the possibility of static linking really
> > fouls up the scheme, and we haven't figured out a good way around this
> > yet. :-(
>
> So pkg-config addresses this with it's Libs.private field and an
> explicit command-li
I'm afraid I don't have any clues offhand. We *have* had problems with the
Pathscale compiler in the past that were never resolved by their support crew.
However, they were of the "variables weren't initialized and the process
generally aborts" kind of failure, not a "persistent hang" kind of
On Mon, 25 Jan 2010 09:09:47 -0500, Jeff Squyres wrote:
> The short version is that the possibility of static linking really
> fouls up the scheme, and we haven't figured out a good way around this
> yet. :-(
So pkg-config addresses this with it's Libs.private field and an
explicit command-line
I have some simple questions for all you users out there about the OMPI FAQ. I
ask because we see a LOT of you end up on the OMPI FAQ in our web statistics
(most users who search either end up on the FAQ and/or on the web archives of
the mailing list). Hence, I'd like to know if we can improve
I am not able to reproduce this problem with the 1.4 branch using a
hostfile, and node configuration like you mentioned.
I suspect that the error is caused by a failed local checkpoint. The
error message is triggered when the global coordinator (located in
'mpirun') tries to read the metada
Hello,
I built OpenMPI-1.4.1 without openib support with the following
configuration options:
./configure
--prefix=/develop/libs/OpenMPI/openmpi-1.4.1/LINUX_GCC_4_1_tcp_mach
--enable-static --enable-shared --enable-cxx-exceptions
--enable-mpi-f77 --disable-mpi-f90 --enable-mpi-cxx
--disable
I tested the 1.4.1 release, and everything worked fine for me (tested
a few different configurations of nodes/environments).
The ompi-checkpoint error you cited is usually caused by one of two
things:
- The PID specified is wrong (which I don't think that is the case
here)
- The session
Yes, it might be necessary. Done in r22473.
Thanks,
Shiqing
Jeff Squyres wrote:
Should this kind of info be added to README.windows?
On Jan 25, 2010, at 4:34 AM,
wrote:
Thanks, that second part about the wrappers was what I was looking for.
Charlie ...
Original Message -
On Jan 25, 2010, at 7:11 AM, Dave Love wrote:
> What's the status of (stabilizing and?) versioning libraries? If I
> recall correctly, it was supposed to be defined as fixed for some
> release period as of 1.3.something.
Correct. We started with 1.3.2 or 1.3.3, IIRC...? I'd have to go back and
Should this kind of info be added to README.windows?
On Jan 25, 2010, at 4:34 AM,
wrote:
> Thanks, that second part about the wrappers was what I was looking for.
>
> Charlie ...
>
> Original Message
> Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)
>
Am Montag, den 25.01.2010, 12:11 + schrieb Dave Love:
> I assumed that the libraries would then be versioned (at least for ELF
> -- I don't know about other formats) and we could remove a major source
> of grief from dynamically linking against the wrong thing, and I think
> Jeff said that woul
Hello:
I'm having some issues with Open MPI 1.4.1 and Pathscale compiler
(version 3.2). Open MPI builds successfully with the following configure
arguments:
./configure --with-openib=/usr --with-openib-libdir=/usr/lib64
--with-sge --enable-static CC=pathcc CXX=pathCC F77=pathf90 F90=pathf90
FC=pa
What's the status of (stabilizing and?) versioning libraries? If I
recall correctly, it was supposed to be defined as fixed for some
release period as of 1.3.something.
I assumed that the libraries would then be versioned (at least for ELF
-- I don't know about other formats) and we could remove
So? anyone? any clue?
Summarize:
- installed OpenMPI 1.4.1 on fresh Centos 5
- mpirun works but ompi-checkpoint throws this error:
ORTE_ERROR_LOG: Not found in file orte-checkpoint.c at line 405
- on another VM I have OpenMPI 1.3.3. installed. Checkpointing works fine on
guest but has the previous
Thanks, that second part about the wrappers was what I was looking for.
Charlie ...
Original Message Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)From: Shiqing Fan Date: Mon, January 25, 2010 2:09 amTo: cjohn...@valverdecomputing.comCc: Open MPI Users Hi
Hi Charlie,
Actually, to compile and link your application with Open MPI on Windows
is similar as on Linux. You have to link your application against the
generated Open MPI libraries, e.g. libopen-mpi.lib (don't forget the
suffix 'd' if you build debug version of the OMPI libraries, e.g.
lib
OK, so I'm a little farther on and perplexed.
As I said, Visual C++ 2005 (release 8.0.50727.867) build of OpenMPI 1.4, using CMake 2.6.4, built everything and it all linked.
Went ahead and built the PACKAGE item in the OpenMPI.sln project, which made a zip file and an installer (although it was
25 matches
Mail list logo
