On Mon, Oct/06/2008 12:24:48PM, Ray Muno wrote:
> Ethan Mallove wrote:
>
> >> Now I get farther along but the build fails at (small excerpt)
> >>
> >> mutex.c:(.text+0x30): multiple definition of `opal_atomic_cmpset_32'
> >> asm/.libs/libasm.a(asm.o):asm.c:(.text+0x30): first defined here
> >> thr
Ethan Mallove wrote:
>> Now I get farther along but the build fails at (small excerpt)
>>
>> mutex.c:(.text+0x30): multiple definition of `opal_atomic_cmpset_32'
>> asm/.libs/libasm.a(asm.o):asm.c:(.text+0x30): first defined here
>> threads/.libs/mutex.o: In function `opal_atomic_cmpset_64':
>> mu
On Sat, Oct/04/2008 11:21:27AM, Raymond Muno wrote:
> Raymond Muno wrote:
>> Raymond Muno wrote:
>>> We are implementing a new cluster that is InfiniBand based. I am working
>>> on getting OpenMPI built for our various compile environments. So far it
>>> is working for PGI 7.2 and PathScale 3.1.
Raymond Muno wrote:
Raymond Muno wrote:
We are implementing a new cluster that is InfiniBand based. I am
working on getting OpenMPI built for our various compile
environments. So far it is working for PGI 7.2 and PathScale 3.1. I
found some workarounds for issues with the Pathscale compilers
Raymond Muno wrote:
We are implementing a new cluster that is InfiniBand based. I am
working on getting OpenMPI built for our various compile environments.
So far it is working for PGI 7.2 and PathScale 3.1. I found some
workarounds for issues with the Pathscale compilers (seg faults) in
the
We are implementing a new cluster that is InfiniBand based. I am
working on getting OpenMPI built for our various compile environments.
So far it is working for PGI 7.2 and PathScale 3.1. I found some
workarounds for issues with the Pathscale compilers (seg faults) in the
OpenMPI FAQ.
When
