Might I chip in and ask "why in the name of fortran are you using -r8"?
It seems like you do not really need it, more that it is a convenience flag
for you (so that you have to type less?)?
Again as I stated in my previous mail, I would never do that (and would
discourage the use of it for almost all causes), especially as linking
against libraries might, as in this case, be limiting your capabilities
(unless you of course compile everything with r8).

Instead do:
integer, parameter :: dp = selected_real_kind(p=14)
real(dp) :: RR(2), QQ(4)

then compile with "mpif90 -c *.f90"

Put the dp variable in some global module :
module precision
public
integer, parameter :: dp = selected_real_kind(p=14)
end module

2014-10-03 14:55 GMT+00:00 Diego Avesani <diego.aves...@gmail.com>:

> Dear Jeff,
> how can I do that?
>
> Do I need to re-install OMPI?
>
> Thanks again
>
>
>
>
>
> Diego
>
>
> On 3 October 2014 16:47, Jeff Squyres (jsquyres) <jsquy...@cisco.com>
> wrote:
>
>> On Oct 3, 2014, at 10:38 AM, Diego Avesani <diego.aves...@gmail.com>
>> wrote:
>>
>> > Dear all, Dear Jeff,
>> > when I use
>> > use MPI, I get
>> >
>> > /tmp/ifortiW8IBH.i90: catastrophic error: **Internal compiler error:
>> segmentation violation signal raised** Please report this error along with
>> the circumstances in which it occurred in a Software Problem Report.  Note:
>> File and line given may not be explicit cause of this error.
>> > compilation aborted for SPH_MPI.f90 (code 1)
>>
>> Sounds like you need to upgrade your compiler to get the latest
>> updates/bug fixes.
>>
>> > If i use "use mpi_f08", I get
>> >
>> >
>> > SPH_MPI.f90(43): error #6285: There is no matching specific subroutine
>> for this generic subroutine call.   [MPI_CART_CREATE]
>> >    CALL MPI_CART_CREATE
>> (MPI_COMM_WORLD,ndims,dims,periods,.TRUE.,COMM_CART,MPI%iErr)
>> > --------^
>>
>> Sounds like you might have mistakes in this part of the code.
>>
>> But note that mpi_f08 involves *changes* to your code, compared to the
>> mpif.h and mpi interfaces -- all MPI handles, for example, have distinct
>> types now -- they're not integers.  For example, you'll need something like
>> this:
>>
>>   type(MPI_Comm) :: COMM_CART
>>
>> > about mpif90 -r8 *.f90
>> > when I istalled open MPI I run
>> >
>> > ./configure --prefix/opt/openmpi cc=icc cxx=icpc f77=ifort FC=ifort
>>
>> F77 is ignored these days; FC is the only one that matters.  And I assume
>> "cc" and "cxx" were typos; I assume you actually used "CC" and "CXX", right?
>>
>> If you're going to compile your application with -r8, then you need to
>> configure OMPI with -r8, e.g., add "FCFLAGS=-r8" in there.  I don't
>> remember what that other flag was you specified offhand, but if it's
>> important, then you need to specify it on the configure command line, for
>> whichever compiler flags are relevant.
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> _______________________________________________
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post:
>> http://www.open-mpi.org/community/lists/users/2014/10/25446.php
>>
>
>
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2014/10/25447.php
>



-- 
Kind regards Nick

Reply via email to