I took care of it - thanks!
On Sep 16, 2014, at 7:36 AM, tmish...@jcity.maeda.co.jp wrote:
> Gilles,
>
> Your patch looks good to me and I think this issue should be fixed
> in the upcoming openmpi-1.8.3. Could you commit it to the trunk and
> create a CMR for it?
>
> Tetsuya
>
>>
Gilles,
Your patch looks good to me and I think this issue should be fixed
in the upcoming openmpi-1.8.3. Could you commit it to the trunk and
create a CMR for it?
Tetsuya
> Mishima-san,
>
> the root cause is macro expansion does not always occur as one would
> have expected ...
>
> could you
Gilles,
Thank you for your fix. I successfully compiled it with PGI, although
I could not check it executing actual test run.
Tetsuya
> Mishima-san,
>
> the root cause is macro expansion does not always occur as one would
> have expected ...
>
> could you please give a try to the attached patch
Mishima-san,
the root cause is macro expansion does not always occur as one would
have expected ...
could you please give a try to the attached patch ?
it compiles (at least with gcc) and i made zero tests so far
Cheers,
Gilles
On 2014/09/01 10:44, tmish...@jcity.maeda.co.jp wrote:
> Hi
Hi folks,
I tried to build openmpi-1.8.2 with PGI fortran and -i8(64bit fortran int)
option
as shown below:
./configure \
--prefix=/home/mishima/opt/mpi/openmpi-1.8.2-pgi14.7_int64 \
--enable-abi-breaking-fortran-status-i8-fix \
--with-tm \
--with-verbs \
--disable-ipv6 \
CC=pgcc CFLAGS="-tp
