[mvapich-discuss] Intel compilers v16 problems
Adam T. Moody
moody20 at llnl.gov
Tue Jun 7 20:13:19 EDT 2016
Hi Jonathan,
I've worked around the missing C functions by applying this patch after
applying the patch you sent earlier. This new attached patch undoes
some of the changes from your patch by dropping a few Fortran 2008
bindings that are missing their corresponding C definitions.
-Adam
Jonathan Perkins wrote:
>Thanks for the hint(s). It may be that some of the bind operatives are not
>valid for the symbols that we have available with this version. No file
>currently defines PMPIX_Aint_add. I'll look at this further.
>
>On Thu, Jun 2, 2016 at 12:54 PM Moody, Adam T. <moody20 at llnl.gov> wrote:
>
>
>
>>No, wait, my previous email was misleading. It's the C definitions that
>>are missing.
>>
>>Which file defines PMPIX_Aint_add?
>>-Adam
>>
>>------------------------------
>>*From:* Moody, Adam T.
>>*Sent:* Thursday, June 02, 2016 9:08 AM
>>*To:* Jonathan Perkins
>>
>>*Cc:* Kenneth Raffenetti; Troy Baer; mvapich-discuss at cse.ohio-state.edu
>>*Subject:* RE: [mvapich-discuss] Intel compilers v16 problems
>>
>>Hi Jonathan,
>>I'm away on travel, and will try to get you a reproducer later if needed.
>>In the meantime, here's another clue. It looks like all missing symbols
>>are defined here:
>>
>>src/binding/fortran/use_mpi_f08/pmpi_f08.f90
>>
>>I see there are lots of "PMPI" symbols in this file, and those are
>>compiled in. It looks like it lost all of the symbols starting with
>>"PMPIX". I've seen this kind of thing before where there is an autotools
>>component that filters the exposed symbols based on whitelisted prefix
>>strings.
>>
>>There are some PMPIX_ symbols for the FT calls like
>>COMM_AGREE/REVOKE/SHRINK which have been successfully compiled in.
>>-Adam
>>
>>*From:* Jonathan Perkins [perkinjo at cse.ohio-state.edu]
>>*Sent:* Friday, May 27, 2016 12:28 PM
>>*To:* Moody, Adam T.
>>*Cc:* Kenneth Raffenetti; Troy Baer; mvapich-discuss at cse.ohio-state.edu
>>*Subject:* Re: [mvapich-discuss] Intel compilers v16 problems
>>
>>Thanks for the feedback Adam. We haven't seen this on our side but maybe
>>we have just been "lucky". Can you send us the steps to reproduce this?
>>We'll take a look at this to make sure that this issue is not present in
>>our next release and to see if we can resolve the issue for you.
>>
>>On Fri, May 27, 2016 at 3:23 PM Adam T. Moody <moody20 at llnl.gov
>><http://UrlBlockedError.aspx>> wrote:
>>
>>
>>
>>>Hi Jonathan,
>>>I guess we're not out of the woods yet. Someone got around to trying to
>>>build a Fortran program with Intel compiler using this patched MPI
>>>build. However, the build fails because apparently the patch adds some
>>>symbols, but the definitions for those symbols are missing:
>>>
>>>
>>>mpif90 -o mpiHello mpiHello.f90
>>>.../libmpifort.so: undefined reference to `PMPIX_Aint_diff'
>>>.../libmpifort.so: undefined reference to `MPIR_File_iread_at_all_cdesc'
>>>.../libmpifort.so: undefined reference to `MPIR_File_iwrite_all_cdesc'
>>>.../libmpifort.so: undefined reference to `MPIR_File_iwrite_at_all_cdesc'
>>>.../libmpifort.so: undefined reference to `MPIR_File_iread_all_cdesc'
>>>.../libmpifort.so: undefined reference to `PMPIX_Aint_add'
>>>
>>>
>>>nm /libmpifort.so | grep PMPIX
>>> U PMPIX_Aint_add
>>> U PMPIX_Aint_diff
>>>000000000004f100 W PMPIX_COMM_AGREE
>>>000000000004f0a0 W PMPIX_COMM_FAILURE_ACK
>>>000000000004f0c0 W PMPIX_COMM_FAILURE_GET_ACKED
>>>000000000004f0d0 W PMPIX_COMM_REVOKE
>>>000000000004f0f0 W PMPIX_COMM_SHRINK
>>>
>>>
>>>grep PMPIX_ *.patch
>>>0001-6-commits-related-to-fortran-binding.patch:+ bind(C,
>>>name="PMPIX_Aint_add") result(res)
>>>0001-6-commits-related-to-fortran-binding.patch:+ bind(C,
>>>name="PMPIX_Aint_diff") result(res)
>>>
>>>
>>>Looks like we'll need a bigger patch. :-)
>>>-Adam
>>>
>>>
>>>Moody, Adam T. wrote:
>>>
>>>
>>>
>>>>Thanks, Jonathan.
>>>>The patch applied cleanly, and the first parallel make with the Intel 16
>>>>
>>>>
>>>compilers worked.
>>>
>>>
>>>>-Adam
>>>>
>>>>________________________________
>>>>From: Jonathan Perkins [perkinjo at cse.ohio-state.edu
>>>>
>>>>
>>><http://UrlBlockedError.aspx>]
>>>
>>>
>>>>Sent: Thursday, April 28, 2016 9:26 AM
>>>>To: Moody, Adam T.; Kenneth Raffenetti
>>>>Cc: Troy Baer; mvapich-discuss at cse.ohio-state.edu
>>>>
>>>>
>>><http://UrlBlockedError.aspx>
>>>
>>>
>>>>Subject: Re: [mvapich-discuss] Intel compilers v16 problems
>>>>
>>>>Thanks Adam. I apologize for the delay. It took me some time to
>>>>
>>>>
>>>determine the correct subset of patches to take from MPICH which allows for
>>>both vpath and parallel builds to work without causing additional problems
>>>(requiring other patches). I believe that I have the right combination
>>>now. I am attaching a single patch which combines 6 patches from MPICH.
>>>The main updates are to build the f08 fortran bindings in their own
>>>directory and adding some bindings which where previously not present.
>>>
>>>
>>>>Adam, can you let us know if this works well for you or if you still see
>>>>
>>>>
>>>some issues within your build system. We're also taking this through our
>>>QA and will be present in our next release if we don't find any problems.
>>>
>>>
>>>>Kenneth, for your info these are the 6 I ended up taking:
>>>>[jperkins at ws31 mvapich2]$ git log --oneline master..
>>>>2c78990 Add F08 bindings for nonblocking collective I/O
>>>>2e1e17a Add F08 bindings for MPI_Aint_add/diff
>>>>9dd9bab binding/f08: install all f08 module header files
>>>>bbd5445 binding/f08: fix vpath builds
>>>>b9067b7 Revise F08 binding build system
>>>>3070dfa Change file extension from .F90 to .f90 in mpi_f08
>>>>
>>>>The hashes may not match up with MPICH's repo as these where
>>>>
>>>>
>>>cherry-picked onto our sources.
>>>
>>>
>>>>On Sat, Apr 23, 2016 at 9:24 PM Moody, Adam T. <moody20 at llnl.gov
>>>>
>>>>
>>><http://UrlBlockedError.aspx><redir.aspx?REF=LAjvqBQxgDGZaIMrQPHQXGd8S0zxplF4kWySmxFA9Pfm5DjnN3HTCAFtYWlsdG86bW9vZHkyMEBsbG5sLmdvdg..>>
>>>wrote:
>>>
>>>
>>>>Hi Jonathan,
>>>>Yes, I have two mvapich tarballs. The first is the original w/o the
>>>>
>>>>
>>>patch, the second is the patched + autogen'd version.
>>>
>>>
>>>>-Adam
>>>>
>>>>________________________________
>>>>From: Jonathan Perkins [perkinjo at cse.ohio-state.edu
>>>>
>>>>
>>><http://UrlBlockedError.aspx>
>>><redir.aspx?REF=oGk20-dlH8rgvfA_leZmLxcx9-VmdZLnGCHBbDNKLfjm5DjnN3HTCAFtYWlsdG86cGVya2luam9AY3NlLm9oaW8tc3RhdGUuZWR1>]
>>>
>>>
>>>>Sent: Saturday, April 23, 2016 4:42 PM
>>>>To: Moody, Adam T.; Kenneth Raffenetti
>>>>
>>>>Cc: Troy Baer; mvapich-discuss at cse.ohio-state.edu
>>>>
>>>>
>>><http://UrlBlockedError.aspx>
>>><redir.aspx?REF=YYTkQ2mtysxbF0Pvy4Yk58jEI2DR6t2plXb17wuyKxPm5DjnN3HTCAFtYWlsdG86bXZhcGljaC1kaXNjdXNzQGNzZS5vaGlvLXN0YXRlLmVkdQ..>
>>>
>>>
>>>>Subject: Re: [mvapich-discuss] Intel compilers v16 problems
>>>>Hi Adam. Thanks for the investigation. I didn't see this followup
>>>>
>>>>
>>>issue but I'll try the steps as you've described it. It wasn't explicitly
>>>mentioned in your email but I'm assuming that you ran autogen.sh after
>>>every application of the patch.
>>>
>>>
>>>>On Sat, Apr 23, 2016 at 4:34 PM Moody, Adam T. <moody20 at llnl.gov
>>>>
>>>>
>>><http://UrlBlockedError.aspx><redir.aspx?REF=DFyS6UUYYuK_0ZLgl00KNj_7Wdrdvlvqvb_Nj2OxeSfm5DjnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9SklJaWZqdFByVXAwT3JPd1BmQzR6R3NuNlN6TGVYUGJjd0dPOVM0LW4zaVVab1czM212VENBRnRZV2xzZEc4NmJXOXZaSGt5TUVCc2JHNXNMbWR2ZGcuLg..>>
>>>wrote:
>>>
>>>
>>>>Hi Jonathan,
>>>>Good news, strange news. First, the patch definitely helps, so thanks
>>>>
>>>>
>>>for that!
>>>
>>>
>>>>My first attempt with it succeeded. This was an in-tree build. I then
>>>>
>>>>
>>>tried an out-of-tree build, and that worked too. Then today, I decided to
>>>try an out-of-tree build w/o the patch and that failed just as before. So
>>>far, so good.
>>>
>>>
>>>>Then things got strange. I went back to the out-of-tree build w/ the
>>>>
>>>>
>>>patch, but this time it failed. This attempt should have been identical to
>>>the first try that worked, because it executes commands saved as an rpm
>>>spec file that is stored as a tagged branch in an svn repo. However, this
>>>time it failed with the following error:
>>>
>>>
>>>>../src/binding/fortran/use_mpi_f08/mpi_c_interface_glue.F90(143): error
>>>>
>>>>
>>>#7013: This module file was not generated by any release of this compiler.
>>> [MPI_F08]
>>>
>>>
>>>> use :: mpi_f08, only : MPI_ADDRESS_KIND, MPI_Comm,
>>>>
>>>>
>>>MPI_Comm_delete_attr_function
>>>
>>>
>>>>-----------^
>>>>
>>>>That error suggests the mpi_f08.mod is of the wrong file format. I
>>>>
>>>>
>>>double checked that it used ifort to compile the module file. Strange.
>>>
>>>
>>>>Looking back through the make output, it's interesting that it printed
>>>>
>>>>
>>>lines about compiling the mpi_f08.mod file just before it started to
>>>compile mpi_c_interface_glue.F90.
>>>
>>>
>>>>/bin/sh ./libtool --tag=FC --mode=compile ifort
>>>>
>>>>
>>>-Isrc/binding/fortran/use_mpi -Isrc/binding/fortran/use_mpi -g -O3 -g -O2
>>>-module src/binding/fortran/use_mpi -c
>>>../src/binding/fortran/use_mpi_f08/`echo
>>>src/binding/fortran/use_mpi/mpi_f08.mod | cut -f1 -d '.' | sed -e
>>>'s+.*/++g'`.F90 -o src/binding/fortran/use_mpi_f08/`echo
>>>src/binding/fortran/use_mpi/mpi_f08.mod | cut -f1 -d '.' | sed -e
>>>'s+.*/++g'`.lo
>>>
>>>
>>>>libtool: compile: ifort -Isrc/binding/fortran/use_mpi
>>>>
>>>>
>>>-Isrc/binding/fortran/use_mpi -g -O3 -g -O2 -module
>>>src/binding/fortran/use_mpi -c
>>>../src/binding/fortran/use_mpi_f08/mpi_f08.F90 -fPIC -o
>>>src/binding/fortran/use_mpi_f08/.libs/mpi_f08.o
>>>
>>>
>>>>libtool: compile: ifort -Isrc/binding/fortran/use_mpi
>>>>
>>>>
>>>-Isrc/binding/fortran/use_mpi -g -O3 -g -O2 -module
>>>src/binding/fortran/use_mpi -c
>>>../src/binding/fortran/use_mpi_f08/mpi_f08.F90 -o
>>>src/binding/fortran/use_mpi_f08/mpi_f08.o >/dev/null 2>&1
>>>
>>>
>>>>/bin/sh ./libtool --tag=FC --mode=compile ifort
>>>>
>>>>
>>>-Isrc/binding/fortran/use_mpi -Isrc/binding/fortran/use_mpi -g -O3 -g -O2
>>>-module src/binding/fortran/use_mpi -c
>>>../src/binding/fortran/use_mpi_f08/`echo
>>>src/binding/fortran/use_mpi/mpi_c_interface_glue.mod | cut -f1 -d '.' | sed
>>>-e 's+.*/++g'`.F90 -o src/binding/fortran/use_mpi_f08/`echo
>>>src/binding/fortran/use_mpi/mpi_c_interface_glue.mod | cut -f1 -d '.' | sed
>>>-e 's+.*/++g'`.lo
>>>
>>>
>>>>I then tried the in-tree build with the patch (again the same that had
>>>>
>>>>
>>>worked once before), but now that failed with an error like the following:
>>>
>>>
>>>>make[2]: ***
>>>>
>>>>
>>>[src/binding/fortran/use_mpi_f08/lib_libmpifort_la-pmpi_f08.lo] Error 1
>>>
>>>
>>>>make[2]: *** Waiting for unfinished jobs....
>>>>make[2]: ***
>>>>
>>>>
>>>[src/binding/fortran/use_mpi_f08/lib_libmpifort_la-mpi_f08.lo] Error 1
>>>
>>>
>>>>I couldn't find any more detailed error messages to go with that, so
>>>>
>>>>
>>>it's less clear what happened in this case. Anyway, between these two
>>>different failures and the fact that seemingly identical build attempts had
>>>both worked once before, it's starting to feel like there may be a race
>>>condition in the build process.
>>>
>>>
>>>>All of these were running parallel make with -j8. I decided to drop the
>>>>
>>>>
>>>-j8 to go back to a serial make. I tried two different builds with serial
>>>make, and both attempts completed w/o error.
>>>
>>>
>>>>I'm now batting 2-for-2 with serial make but only hitting 2-for-5 with
>>>>
>>>>
>>>parallel make.
>>>
>>>
>>>>So the short story. The patch helps for sure. There's still something
>>>>
>>>>
>>>strange going on in the F90 build, perhaps a race condition when using
>>>parallel make.
>>>
>>>
>>>>-Adam
>>>>
>>>>
>>>>________________________________
>>>>From: Jonathan Perkins [perkinjo at cse.ohio-state.edu
>>>>
>>>>
>>><http://UrlBlockedError.aspx>
>>><redir.aspx?REF=T9Mf0FCrktiWn9unoIQ44KLb7jYTcGKZET9B92PAIIXm5DjnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9WVpacEo0NHFLdjZkV1hoTFBOSkZpS0k2NUhEYVExUVc1UF9BVFhVakZKMlVab1czM212VENBRnRZV2xzZEc4NmNHVnlhMmx1YW05QVkzTmxMbTlvYVc4dGMzUmhkR1V1WldSMQ..>]
>>>
>>>
>>>>Sent: Friday, April 22, 2016 11:32 AM
>>>>To: Kenneth Raffenetti; Moody, Adam T.
>>>>Cc: Troy Baer; mvapich-discuss at cse.ohio-state.edu
>>>>
>>>>
>>><http://UrlBlockedError.aspx>
>>><redir.aspx?REF=rVMMtAbSxqNDf6hrLpRszYlc8ioJgLjhYcshFdTOaUfm5DjnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9dFFzQl9mS3pYR242WUEzY2h0dC1vcDFYMGFYX3EtaTYya0ZtZjZWRVh2aVVab1czM212VENBRnRZV2xzZEc4NmJYWmhjR2xqYUMxa2FYTmpkWE56UUdOelpTNXZhR2x2TFhOMFlYUmxMbVZrZFEuLg..>
>>>
>>>
>>>>Subject: Re: [mvapich-discuss] Intel compilers v16 problems
>>>>
>>>>It appears that whatever I was doing last night may have been checked
>>>>
>>>>
>>>properly because when I run (or did not run) ./autogen.sh. In the end it
>>>appears that only the attached patch was necessary. Adam, can you try this
>>>out and let us know if it resolves your issue?
>>>
>>>
>>>>Please remember to run autogen.sh and configuere again after applying
>>>>
>>>>
>>>this patch.
>>>
>>>
>>>>On Fri, Apr 22, 2016 at 1:25 PM Jonathan Perkins <
>>>>
>>>>
>>>perkinjo at cse.ohio-state.edu <http://UrlBlockedError.aspx><redir.aspx?REF=uYxm5Z4PcVF-FjVP7LxPJRGCIG8s39qHG4BVnHGU26BIRjvnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9ci1VZG5PTWxNdERWUjJyY3E2MHhEOWk0TXVqVXpvVGgxVTZBQU5pNno4eVVab1czM212VENBRm9kSFJ3T2k4dmNtVmthWEl1WVhOd2VEOVNSVVk5UjJkNVIxcHlZblEzWlV0ME5VSjZWa05aVTJoWlN6TTNkbVpIUnpBeWFtTnFUM0Z5WkhSV1pWY3laVFpaVW5KcGNUSjJWRU5CUm5SWlYyeHpaRWM0Tm1OSFZubGhNbXgxWVcwNVFWa3pUbXhNYlRsdllWYzRkR016VW1oa1IxVjFXbGRTTVEuLg..>>
>>>wrote:
>>>
>>>
>>>>Hi guys. I tried to backport the first patch Ken pointed out last night
>>>>
>>>>
>>>but ran into some issues that may or may not be related to his next patch.
>>>I'm going to work on this a bit more and let you know whether we have a
>>>working patch or not.
>>>
>>>
>>>>On Fri, Apr 22, 2016 at 12:21 PM Kenneth Raffenetti <
>>>>
>>>>
>>>raffenet at mcs.anl.gov <http://UrlBlockedError.aspx><redir.aspx?REF=14dLmciCXMKSfWT00vrQZR5rsghAI6XQCBKPw_YWK2tIRjvnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9MlFqRE1YRldPTkd6MXBqdklJWHdUMU9pNTBHbkszQ3ZNVDN4OUlkYk9JV1Vab1czM212VENBRm9kSFJ3T2k4dmNtVmthWEl1WVhOd2VEOVNSVVk5U0VoaWFrUmplR2xZVTNVNWFGRmlVek5uVUVwTlpuZ3hTazAwTmpNMVZIcERNRzlOV1VZeGNqRlFMVFpaVW5KcGNUSjJWRU5CUm5SWlYyeHpaRWM0Tm1OdFJtMWFiVloxV2xoU1FXSlhUbnBNYlVaMVlrTTFibUl6V1M0Lg..>>
>>>wrote:
>>>
>>>
>>>>There may be other stragglers, but try cherry-picking this one.
>>>>
>>>>
>>>>
>>>http://git.mpich.org/mpich.git/commitdiff/0750f10fcab0a04b33a86ff12ca95739c7376a27
>>><http://UrlBlockedError.aspx>
>>><redir.aspx?REF=c6zmGMg46Kmef4SMBFIxpWRDaskjP0fhu9hHAvQPQyxIRjvnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9MkI0QUpkZS16VHdsSVU5MzE5ZUMwLVplSHNCbWxLVnhSckZWUHJUb0FKdVVab1czM212VENBRm9kSFJ3T2k4dmNtVmthWEl1WVhOd2VEOVNSVVk5YjFWWmEzY3RRblpYUldGV09YRlVNMkUxVmxSbmFTMDJZMnd0UTNkeGVEazBVbmgxYXpGbFNUZDJhVFpaVW5KcGNUSjJWRU5CUm05a1NGSjNUMms0ZG1NeVZtcGtXRXBzVEZoa2JGbHBOV3BoV0U1cVluazFhbUl5TUhaTldGcGFWVzVvV2sxRmVERmpiVEIwVGpKT2JsRldVVEZNVkVJMlpWUkNlV0ZWYUZCYVdGVTBaRmRHTlZGdWFEQmlSRUUwVkRGT1RtTXlTVFJrYlhSb1RVVnNXRTFIVGtwamVrSnZXV3BXYzFwWGJGbGpiVGxYVmtkT2FtTjZSbGhrTUd4RFRVaENNbFl4VVhSV1ZrcFZVV3BLV2xvelJYZFJWR2N4V1ZWTmQxUjVNVUphZWxaVlRGaFZNbHBHU21sVVZYZzBaR3hvVUUxSGVETk9SRTVHWkRCek5VMHdlRXBpTTI4d1ZHeG9SbUZHVGxobGJIQnJWMjFzTkZGcVRreGtiVTVzVmtoU2EwOUdWbk5pTW5oU1pVVk9jR0pIVmtwUk0yd3lWRmhHU0dFd1NUUmxSMnhMVWtoc2VXRnVRblJTU0ZKMlRVaEdlbFY2VmpGaFZsSnpaRmhTTUZkdFVrdFJWbHBPWlcweGJGWlVWVEpOYkZKWFlVYzVjazU2Vm5sVFNFWnZUVmh3YWxSSFVrSlRiVGxWVFROT2FGRlVaRlpXTWxKS1dqTkZNbFJYV25aalNFWnhZa1ZvY0U1WFVucE9NMHBaV2pCTk1sSXpiREpTTTJoRldXNWtWVTVGVWxsWlZXeFlWRmhvV1UxNlZURlRNbkJIWWtNeGNVNXJkRE5YVkVZeFZFYzVWVlI2YURWUFJsSnJVVEJqTWxwdE5EQmxhM016WlZaS1JWVldVbEZUYTBadFZqQjRTbGRWTlZsWk1teEtXa2hTYWxWNlZraGxWV1JPWVVjMVZXSkhVbEJqYkVaT1lsZFJNMDFGTlVkYWJHeFdWMWMxVlZORmJFOVNSMDVVVmxNNWIyUklVbmRLVkU1Q1NsUktSMHBVU2tkYU1td3dURzB4ZDJGWFRtOU1iVGw1V25sVmVWSnRNWGRoVjA1dlRHMWtjR1JEVlhsU2JVNTJZbGN4Y0dSSFVuQmFiVmxzVFd0WmQwNTZWWGRhYWtWM1dtMU9hRmxxUW1oTlJGSnBUWHBPYUU5RVdtMWFha1Y1V1RKRk5VNVVZM3BQVjAwelRYcGpNbGxVU1RNLg..>
>>>
>>>
>>>>Ken
>>>>
>>>>On 04/21/2016 06:35 PM, Adam T. Moody wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Thanks everyone. That definitely improved things. If I change things
>>>>>to do an in-tree build, it gets past that missing file error. Now it
>>>>>fails when trying to compile the first F08 wrapper. I've cut-and-paste
>>>>>that below too in case it's familiar to someone.
>>>>>
>>>>>Jonathan, if you put together a patch, I'll be happy to try it out.
>>>>>-Adam
>>>>>
>>>>>
>>>>>
>>>>>/bin/sh ./libtool --tag=FC --mode=compile ifort -DHAVE_CONFIG_H -I.
>>>>>-I./src/include -I./src/include -I./src/mpi/datatype -I./src/mpi/spawn
>>>>>-Isrc/util/logging/common -I./src/util/wrappers -I./src/util/wrappers
>>>>>-I./src/binding/cxx
>>>>>-I/builddir/build/BUILD/mvapich/src/src/binding/fortran/mpif_h
>>>>>-Isrc/binding/fortran/use_mpi
>>>>>
>>>>>
>>>>>-I/builddir/build/BUILD/mvapich/src/src/binding/fortran/use_mpi_f08/wrappers_c
>>>>>-I./src/mpid/ch3/include -I./src/mpid/ch3/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpid/ch3/channels/common/include
>>>>>-I./src/mpid/ch3/channels/psm/include -I./src/mpid/common/datatype
>>>>>-I./src/mpid/common/datatype -I./src/mpid/common/sched
>>>>>-I./src/mpid/common/thread -I./src/pmi/simple
>>>>>-Icontrib/hwloc/include/ -I./contrib/hwloc/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpid/ch3/channels/psm/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpid/ch3/channels/psm/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/util/wrappers
>>>>>-I/builddir/build/BUILD/mvapich/src/src/util/wrappers
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpl/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpl/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/openpa/src
>>>>>-I/builddir/build/BUILD/mvapich/src/src/openpa/src -D_REENTRANT
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpi/romio/include
>>>>>-Isrc/binding/fortran/use_mpi -Isrc/binding/fortran/use_mpi -g -O3 -g
>>>>>-O2 -c -o
>>>>>
>>>>>
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/lib_libmpifort_la-abort_f08ts.lo
>>>>>`test -f 'src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90' ||
>>>>>echo './'`src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90
>>>>>
>>>>>
>>>>>libtool: compile: ifort -DHAVE_CONFIG_H -I. -I./src/include
>>>>>-I./src/include -I./src/mpi/datatype -I./src/mpi/spawn
>>>>>-Isrc/util/logging/common -I./src/util/wrappers -I./src/util/wrappers
>>>>>-I./src/binding/cxx
>>>>>-I/builddir/build/BUILD/mvapich/src/src/binding/fortran/mpif_h
>>>>>-Isrc/binding/fortran/use_mpi
>>>>>
>>>>>
>>>>>-I/builddir/build/BUILD/mvapich/src/src/binding/fortran/use_mpi_f08/wrappers_c
>>>>>-I./src/mpid/ch3/include -I./src/mpid/ch3/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpid/ch3/channels/common/include
>>>>>-I./src/mpid/ch3/channels/psm/include -I./src/mpid/common/datatype
>>>>>-I./src/mpid/common/datatype -I./src/mpid/common/sched
>>>>>-I./src/mpid/common/thread -I./src/pmi/simple -Icontrib/hwloc/include/
>>>>>-I./contrib/hwloc/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpid/ch3/channels/psm/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpid/ch3/channels/psm/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/util/wrappers
>>>>>-I/builddir/build/BUILD/mvapich/src/src/util/wrappers
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpl/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpl/include
>>>>>-I/builddir/build/BUILD/mvapich/src/src/openpa/src
>>>>>-I/builddir/build/BUILD/mvapich/src/src/openpa/src -D_REENTRANT
>>>>>-I/builddir/build/BUILD/mvapich/src/src/mpi/romio/include
>>>>>-Isrc/binding/fortran/use_mpi -Isrc/binding/fortran/use_mpi -g -O3 -g
>>>>>-O2 -c src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90 -fPIC
>>>>>-o
>>>>>
>>>>>
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/.libs/lib_libmpifort_la-abort_f08ts.o
>>>>>
>>>>>
>>>>>
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(8): error
>>>>>#7005: Error in reading the compiled module file. [MPI_F08]
>>>>> use :: mpi_f08, only : MPI_Comm
>>>>>-----------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(14): error
>>>>>#6406: Conflicting attributes or multiple declaration of name.
>>>>>
>>>>>
>>> [MPI_COMM]
>>>
>>>
>>>>> type(MPI_Comm), intent(in) :: comm
>>>>>---------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(18): error
>>>>>#6683: A kind type parameter must be a compile-time constant. [C_COMM]
>>>>> integer(c_Comm) :: comm_c
>>>>>------------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(23): error
>>>>>#6404: This name does not have a type, and must have an explicit type.
>>>>>[MPIR_ABORT_C]
>>>>> ierror_c = MPIR_Abort_c(comm%MPI_VAL, errorcode)
>>>>>-------------------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(25): error
>>>>>#6404: This name does not have a type, and must have an explicit type.
>>>>>[COMM]
>>>>> comm_c = comm%MPI_VAL
>>>>>-----------------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(25): error
>>>>>#6460: This is not a field name that is defined in the encompassing
>>>>>structure. [MPI_VAL]
>>>>> comm_c = comm%MPI_VAL
>>>>>----------------------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(8): error
>>>>>#6580: Name in only-list does not exist. [MPI_COMM]
>>>>> use :: mpi_f08, only : MPI_Comm
>>>>>---------------------------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(9): error
>>>>>#6580: Name in only-list does not exist. [C_COMM]
>>>>> use :: mpi_c_interface, only : c_Comm
>>>>>-----------------------------------^
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90(10): error
>>>>>#6580: Name in only-list does not exist. [MPIR_ABORT_C]
>>>>> use :: mpi_c_interface, only : MPIR_Abort_c
>>>>>-----------------------------------^
>>>>>compilation aborted for
>>>>>src/binding/fortran/use_mpi_f08/wrappers_f/abort_f08ts.F90 (code 1)
>>>>>make[2]: ***
>>>>>
>>>>>
>>>>>[src/binding/fortran/use_mpi_f08/wrappers_f/lib_libmpifort_la-abort_f08ts.lo]
>>>>>Error 1
>>>>>
>>>>>
>>>>>It seems that the compiler can't find the mpi_f08.mod file. From
>>>>>another build, I can see that is in
>>>>>src/binding/fortran/use_mpi/mpi_f08.mod.
>>>>>-Adam
>>>>>
>>>>>
>>>>>Jonathan Perkins wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hi Kenneth. Thanks for pointing out this commit! It looks like this
>>>>>>would
>>>>>>be fix the issue that we've seen reported a few times on this list as
>>>>>>well. Once applied cleanly I'll verify that the issue is resolved and
>>>>>>include this for our future releases.
>>>>>>
>>>>>>On Thu, Apr 21, 2016 at 5:37 PM Kenneth Raffenetti <
>>>>>>
>>>>>>
>>>raffenet at mcs.anl.gov <http://UrlBlockedError.aspx>
>>><redir.aspx?REF=9YXc6nfaGdN_ZIp_uaIf6Ros5zAfCSHuap-iVohXjQBIRjvnN3HTCAFodHRwOi8vcmVkaXIuYXNweD9SRUY9MzNnWjl1T0NQRVpmSGZack5PNEFydW8xTURJZy0tZmx6WF9USDNDVzJqRDF4NGUzM212VENBRm9kSFJ3T2k4dmNtVmthWEl1WVhOd2VEOVNSVVk5U0VoaWFrUmplR2xZVTNVNWFGRmlVek5uVUVwTlpuZ3hTazAwTmpNMVZIcERNRzlOV1VZeGNqRlFMVFpaVW5KcGNUSjJWRU5CUm5SWlYyeHpaRWM0Tm1OdFJtMWFiVloxV2xoU1FXSlhUbnBNYlVaMVlrTTFibUl6V1M0Lg..>>
>>>
>>>
>>>>>>wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>On 04/21/2016 04:13 PM, Troy Baer wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>On 04/21/2016 05:09 PM, Adam T. Moody wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Did you find an answer to this question?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/2015-October/005722.html
>>><http://UrlBlockedError.aspx>
>>><redir.aspx?REF=2HMqXC-KOsckOHbXuLIxOW6C5kwNswWkxmrhkdBtESpIRjvnN3HTCAFodHRwOi8vcmVkaXIu
>>>
>>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: drop_f08.patch
Type: text/x-patch
Size: 23985 bytes
Desc: not available
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20160607/123ade6a/attachment-0001.bin>
More information about the mvapich-discuss
mailing list