nt GCC on the back-end. If you can confirm that pathscale *is*
> using GCC 4.x on the back-end, then this is worth reporting to the
> pathscale support people.
> >
> > I have no problem running the code below compiled with openmpi 1.4.2
> and
> > pathscale 3.2.
>
t;orte_base_help_aggregate" to 0 to see
all help / error messages
There are no problems when Open MPI 1.4.2 is built with GCC (GCC 4.1.2).
No problems are found with Open MPI 1.2.6 and PathScale either.
Best regards,
Rafa
--
Rafael Arco Arredondo
Centro de Servicios de Informática y Redes de Comunicaciones
Campus de Fuentenueva - Edificio Mecenas
Universidad de Granada
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 - Do you have an example code that have problems?
--
Rafael Arco Arredondo
Centro de Servicios de Informática y Redes de Comunicaciones
Universidad de Granada
as able to build previous versions of Open MPI with Pathscale (1.2.6
and 1.3.2, particularly). I tried building version 1.4.1 both with
Pathscale 3.2 and Pathscale 3.1. No difference.
Any ideas?
Thank you in advance,
Rafa
--
Rafael Arco Arredondo
Centro de Servicios de Informática y Redes de Comu