On Tue, 30 Oct 2007, Bogdan Costescu wrote:
Bad timing... I don't have access to the files at the moment, I'll
write back shortly (which probably means tomorrow ;-)).
Here they are:
http://spider.iwr.uni-heidelberg.de/~bogdan/openmpi/
Due to their size, I decided to put them up on a web serv
On Tue, 30 Oct 2007, Tom Mitchell wrote:
No but there are choices in how pathcc can be invoked and thus what
frontend and other chunks are active.
$ pathcc -v
QLogic PathScale(TM) Compiler Suite: Version 3.0
Built on: 2007-02-22 13:05:15 -0800
Thread model: posix
GNU gcc version 4.0.2 (PathSca
On Oct 30 02:06, Bogdan Costescu wrote:
> On Mon, 29 Oct 2007, Tom Mitchell wrote:
>
> > Debian is not supported by the PathScale compiler.
>
> Thanks for your answer. In the meantime I have found a workaround for
> my situation, but I'll answer for the sake of the e-mail archives.
>
> > which
On 29 October 2007 at 20:51, Tom Mitchell wrote:
| I do not know which gcc compiler suite Debian GCC is based on.
Typically several versions of gcc et al are available at the same time --
tab-completing on my Debian testing system gives:
edd@ron:~> gcc-
gcc-3.4 gcc-4.1 gcc-4.2
On Mon, 29 Oct 2007, Tom Mitchell wrote:
Debian is not supported by the PathScale compiler.
Thanks for your answer. In the meantime I have found a workaround for
my situation, but I'll answer for the sake of the e-mail archives.
which one is is being used? The new Debian etch 64bit has min
On Oct 23 08:57, Jeff Squyres wrote:
> On Oct 23, 2007, at 6:33 AM, Bogdan Costescu wrote:
>
> >> There is in the openib BTL.
> >
> > The bug #1025 has in one the answers the following phrase:
> >
> > "It looks like this will affect many threading issues with the
> > pathscale compiler -- the open
On Tue, 23 Oct 2007, Brian Barrett wrote:
--without-memory-manager --enable-mca-static=btl-mx,mtl-mx
From what I understand from the FAQ, the above --enable-mca-static
option would include statically linked MX support in libmpi. But I was
building all support in (--enable-static --disable-
On Oct 23, 2007, at 10:58 AM, Patrick Geoffray wrote:
Bogdan Costescu wrote:
I made some progress: if I configure with "--without-memory-manager"
(along with all other options that I mentioned before), then it
works.
This was inspired by the fact that the segmentation fault occured in
ptmall
Hi Bogdan,
Bogdan Costescu wrote:
I made some progress: if I configure with "--without-memory-manager"
(along with all other options that I mentioned before), then it works.
This was inspired by the fact that the segmentation fault occured in
ptmalloc2. I have previously tried to remove the MX
On Oct 23, 2007, at 10:36 AM, Bogdan Costescu wrote:
I don't get to that point... I am not even able to use the wrapper
compilers (f.e. mpif90) to obtain an executable to run. The
segmentation fault happens when Open MPI utilities are being run, even
ompi_info.
Ahh, I thought you were getting
On Tue, 23 Oct 2007, Scott Atchley wrote:
Which version of MX are you using? Are you enabling the MX
registration cache (regcache)?
Can you try two runs, one exporting MX_RCACHE=1 and one exporting
MX_RCACHE=0 to all processes?
I don't get to that point... I am not even able to use the wrappe
On Oct 23, 2007, at 6:33 AM, Bogdan Costescu wrote:
I made some progress: if I configure with "--without-memory-manager"
(along with all other options that I mentioned before), then it works.
This was inspired by the fact that the segmentation fault occured in
ptmalloc2. I have previously tried
On Oct 23, 2007, at 6:33 AM, Bogdan Costescu wrote:
There is in the openib BTL.
The bug #1025 has in one the answers the following phrase:
"It looks like this will affect many threading issues with the
pathscale compiler -- the openib BTL is simply the first place we
tripped it."
which along
On Mon, 22 Oct 2007, Jeff Squyres wrote:
There is in the openib BTL.
The bug #1025 has in one the answers the following phrase:
"It looks like this will affect many threading issues with the
pathscale compiler -- the openib BTL is simply the first place we
tripped it."
which along with th
On Oct 22, 2007, at 2:49 PM, Bogdan Costescu wrote:
Is there some known incompatibility of the latest stable versions with
the PathScale 3.0 compilers ?
There is in the openib BTL. We've had an open issue with PathScale
for many months. They're able to reproduce the error and have
narr
Is there some known incompatibility of the latest stable versions with
the PathScale 3.0 compilers ?
I have a very puzzling problem with the following combination:
- PathScale 3.0 suite
- Open MPI 1.2.3 and 1.2.4 (both behave the same)
- Debian etch, kernel 2.6.22.9/x86_64 running on AMD Op
16 matches
Mail list logo