Re: [OMPI devel] Open-MX vs OMPI 1.3 using MX internal symbols

2009-01-26 Thread George Bosilca
On Jan 26, 2009, at 15:31 , Brice Goglin wrote: George Bosilca wrote: Yes, the only thing we need is an unique identifier per cluster. We use the last 6 digits from the mapper MAC address. Ok, thanks for the details. We are going to implement all this in Open-MX now. Then, I guess mx__regc

Re: [OMPI devel] Open-MX vs OMPI 1.3 using MX internal symbols

2009-01-26 Thread Brice Goglin
George Bosilca wrote: > Yes, the only thing we need is an unique identifier per cluster. We > use the last 6 digits from the mapper MAC address. Ok, thanks for the details. We are going to implement all this in Open-MX now. >> Then, I guess mx__regcache_clean is called when the OMPI free hook >>

Re: [OMPI devel] Open-MX vs OMPI 1.3 using MX internal symbols

2009-01-26 Thread Jeff Squyres
On Jan 26, 2009, at 9:09 AM, George Bosilca wrote: By the way, is there a way to get more details from OMPI when it fails to load a component because of missing symbols like this? LD_DEBUG=verbose isn't very convenient :) mca_component_show_load_errors is what you need there. Set it to som

Re: [OMPI devel] Open-MX vs OMPI 1.3 using MX internal symbols

2009-01-26 Thread George Bosilca
There are several reasons these calls are there. Please read further. On Jan 26, 2009, at 02:19 , Brice Goglin wrote: Hello, I am testing OpenMPI 1.3 over Open-MX. OpenMPI 1.2 works well but 1.3 does not load. This is caused by OMPI MX components now using some MX internal symbols (mx_open_boa

[OMPI devel] Open-MX vs OMPI 1.3 using MX internal symbols

2009-01-26 Thread Brice Goglin
Hello, I am testing OpenMPI 1.3 over Open-MX. OpenMPI 1.2 works well but 1.3 does not load. This is caused by OMPI MX components now using some MX internal symbols (mx_open_board, mx__get_mapper_state and mx__regcache_clean). This looks like an ugly hack to me :) Why don't you talk to Myricom abou