Re: [Pypar-developers] Problems with pypar & MPICH2

[Ole N. <ole...@gm...>]

Or as it is, it appears that with MPICH the command to get the compiler
string is

mpicc -compile_info -link_info

Could I bother you to paste that in?

Thanks
Ole



On Tue, Dec 22, 2009 at 5:29 AM, Ole Nielsen
<ole...@gm...>wrote:

> OK - then the problem might be with mpicc --showme
> Could I bother you to issue that command (using mpicc from MPICH2) and
> paste the results in.
> With OpenMPI it is
>
> o@desktop:~/sandpit/pypar$ mpicc --showme
> gcc -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -pthread
> -L/usr/lib/openmpi/lib -lmpi -lopen-rte -lopen-pal -ldl -Wl,--export-dynamic
> -lnsl -lutil -lm -ldl
>
> and this works fine.
>
> Cheers
> Ole
>
>
> On Mon, Dec 21, 2009 at 11:42 PM, Jussi Lehtola <
> jus...@fe...> wrote:
>
>> On Mon, 2009-12-21 at 23:38 +1100, Ole Nielsen wrote:
>> > Hi Jussi - this compiles fine where I am, but I am using OpenMPI.
>> > The compiler flags are generated mpicc.
>>
>> I'm, too, a Open MPI user myself.
>>
>> > Does it work if you run python compile_pypar_locally.py - just as a
>> > test.
>>
>> Yes, it works just fine with MPICH2.
>>
>> --
>> Jussi Lehtola
>> Fedora Project Contributor
>> jus...@fe...
>>
>>
>