September 2018 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Yuri 29 Sep '18

29 Sep '18

On 9/28/18 12:29 PM, Si, Min wrote: > > I need to build MPICH on the same FreeBSD version to figure it out. Install into a VM using this ISO image: https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.2/FreeB… In VM, cd /usr/ports/net/mpich && make Yuri _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Si, Min 28 Sep '18

28 Sep '18

It looks like MPICH could not find weak symbol support for some reason. From your log at https://people.freebsd.org/~yuri/mpich-configure.log checking for type of weak symbol alias support... no checking whether __attribute__ ((weak)) allowed... yes checking whether __attribute__ ((weak_import)) allowed... yes checking whether __attribute__((weak,alias(...))) allowed... yes The expected output should be checking for type of weak symbol alias support... pragma weak I need to build MPICH on the same FreeBSD version to figure it out. Min On 2018/09/27 22:16, Yuri wrote: On 9/27/18 7:48 PM, Si, Min wrote: Could you please attache the whole config.log ? I just tried MPICH-3.2.1 on FreeBSD 10.3, it lists both PMPI and MPI symbols. It looks like your build does not contain weak symbols. FreeBSD 10.3 is old, about to become obsolete. Here is the complete configure.log: https://people.freebsd.org/~yuri/mpich-configure.log Yuri _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Yuri 27 Sep '18

27 Sep '18

On 9/27/18 7:48 PM, Si, Min wrote: > Could you please attache the whole config.log ? > > I just tried MPICH-3.2.1 on FreeBSD 10.3, it lists both PMPI and MPI > symbols. It looks like your build does not contain weak symbols. FreeBSD 10.3 is old, about to become obsolete. Here is the complete configure.log: https://people.freebsd.org/~yuri/mpich-configure.log Yuri _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Si, Min 27 Sep '18

27 Sep '18

Could you please attache the whole config.log ? I just tried MPICH-3.2.1 on FreeBSD 10.3, it lists both PMPI and MPI symbols. It looks like your build does not contain weak symbols. > readelf -s install/lib/libmpi.so | grep MPI_Status_c2 > 445: 00000000000e8b60 101 FUNC GLOBAL DEFAULT 10 PMPI_Status_c2f > 1634: 00000000000e8b60 101 FUNC WEAK DEFAULT 10 MPI_Status_c2f > 5014: 00000000000e8b60 101 FUNC GLOBAL DEFAULT 10 PMPI_Status_c2f > 6203: 00000000000e8b60 101 FUNC WEAK DEFAULT 10 MPI_Status_c2f Min On 2018/09/27 21:06, Yuri wrote: > On 9/27/18 6:53 PM, Jeff Hammond wrote: >> Does Fortran configure test for integer size pass? >> > > In the log, every test containing the word "fortran" passes, but none > say "integer size". > > > Yuri > > > > $ grep size configure.log > checking size of void *... 8 > checking size of int... 4 > checking size of char... 1 > checking size of unsigned char... 1 > checking size of short... 2 > checking size of unsigned short... 2 > checking size of int... 4 > checking size of unsigned int... 4 > checking size of long... 8 > checking size of unsigned long... 8 > checking size of long long... 8 > checking size of unsigned long long... 8 > checking size of float... 4 > checking size of double... 8 > checking size of long double... 16 > checking size of void *... 8 > checking size of wchar_t... 4 > checking size of float_int... 8 > checking size of double_int... 16 > checking size of long_int... 16 > checking size of short_int... 8 > checking size of two_int... 8 > checking size of long_double_int... 32 > checking size of _Bool... 1 > checking size of float _Complex... 8 > checking size of double _Complex... 16 > checking size of long double _Complex... 32 > checking for size of Fortran type integer... 4 > checking for size of Fortran type real... 4 > checking for size of Fortran type double precision... 8 > checking size of bool... 1 > checking size of Complex... 8 > checking size of DoubleComplex... 16 > checking size of LongDoubleComplex... 32 > checking for size_t... (cached) yes > checking size of MPIR_Bsend_data_t... 96 > checking size of long long... 8 > checking for size_t... (cached) yes > checking for ssize_t... (cached) yes > checking size of int... 4 > checking size of void *... 8 > checking size of long long... (cached) 8 > checking for blksize_t... yes > checking size of unsigned long... 8 > checking for size_t... (cached) yes > checking size of OPA_ptr_t... 8 > checking the sizeof MPI_Offset... 8 > checking for size of MPI_Status... 20 > configure: WARNING: The ch3 device did not set the maximum size of an > error string, 512 being used. > config.status: creating src/binding/fortran/use_mpi/mpi_sizeofs.f90 > checking size of void *... 8 > checking size of void *... (cached) 8 > checking size of int... 4 > checking size of long... 8 > checking size of long long... 8 > checking size of short... 2 > checking for C integer type of address size... long > config.status: creating f77/ext/add1size.h > config.status: creating f77/rma/addsize.h > config.status: creating errors/f77/io/addsize.h > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Yuri 27 Sep '18

27 Sep '18

On 9/27/18 6:53 PM, Jeff Hammond wrote: > Does Fortran configure test for integer size pass? > In the log, every test containing the word "fortran" passes, but none say "integer size". Yuri $ grep size configure.log checking size of void *... 8 checking size of int... 4 checking size of char... 1 checking size of unsigned char... 1 checking size of short... 2 checking size of unsigned short... 2 checking size of int... 4 checking size of unsigned int... 4 checking size of long... 8 checking size of unsigned long... 8 checking size of long long... 8 checking size of unsigned long long... 8 checking size of float... 4 checking size of double... 8 checking size of long double... 16 checking size of void *... 8 checking size of wchar_t... 4 checking size of float_int... 8 checking size of double_int... 16 checking size of long_int... 16 checking size of short_int... 8 checking size of two_int... 8 checking size of long_double_int... 32 checking size of _Bool... 1 checking size of float _Complex... 8 checking size of double _Complex... 16 checking size of long double _Complex... 32 checking for size of Fortran type integer... 4 checking for size of Fortran type real... 4 checking for size of Fortran type double precision... 8 checking size of bool... 1 checking size of Complex... 8 checking size of DoubleComplex... 16 checking size of LongDoubleComplex... 32 checking for size_t... (cached) yes checking size of MPIR_Bsend_data_t... 96 checking size of long long... 8 checking for size_t... (cached) yes checking for ssize_t... (cached) yes checking size of int... 4 checking size of void *... 8 checking size of long long... (cached) 8 checking for blksize_t... yes checking size of unsigned long... 8 checking for size_t... (cached) yes checking size of OPA_ptr_t... 8 checking the sizeof MPI_Offset... 8 checking for size of MPI_Status... 20 configure: WARNING: The ch3 device did not set the maximum size of an error string, 512 being used. config.status: creating src/binding/fortran/use_mpi/mpi_sizeofs.f90 checking size of void *... 8 checking size of void *... (cached) 8 checking size of int... 4 checking size of long... 8 checking size of long long... 8 checking size of short... 2 checking for C integer type of address size... long config.status: creating f77/ext/add1size.h config.status: creating f77/rma/addsize.h config.status: creating errors/f77/io/addsize.h _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Jeff Hammond 27 Sep '18

27 Sep '18

Does Fortran configure test for integer size pass? On Thu, Sep 27, 2018 at 6:39 PM Yuri <yuri(a)rawbw.com> wrote: > On FreeBSD 11.2, the port net/mpich (version 3.2.1) builds lib/libmpi.so > without MPI_Status_c2f: > > $ readelf -s /usr/local/lib/libmpi.so | grep MPI_Status_c2 > 440: 00000000000e7dc0 98 FUNC GLOBAL DEFAULT 11 PMPI_Status_c2f > > This breaks several dependencies, for ex. mpi4py, see the discussion > here: > > https://bitbucket.org/mpi4py/mpi4py/issues/111/build-failures-but-build-suc… > > > Please help to understand what goes wrong during the port build. > > > Thanks, > > Yuri > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

lib/libmpi.so doesn't contain the MPI_Status_c2f symbol in the FreeBSD mpich package
by Yuri 27 Sep '18

27 Sep '18

On FreeBSD 11.2, the port net/mpich (version 3.2.1) builds lib/libmpi.so without MPI_Status_c2f: $ readelf -s /usr/local/lib/libmpi.so | grep MPI_Status_c2 440: 00000000000e7dc0 98 FUNC GLOBAL DEFAULT 11 PMPI_Status_c2f This breaks several dependencies, for ex. mpi4py, see the discussion here: https://bitbucket.org/mpi4py/mpi4py/issues/111/build-failures-but-build-suc… Please help to understand what goes wrong during the port build. Thanks, Yuri _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Getting an error in MPI_Comm_accept - ideas?
by Amer, Abdelhalim 27 Sep '18

27 Sep '18

Hi, Can you pack the smallest test example in a single file so that we compile and run it? Also please give us more information about the MPICH version you are using and how it was built (run the `mpichversion` binary to get this information). It would be better to use the latest version (3.2.1) before reporting back. All of this is to help us reproduce your problem or simply solving it by upgrading to a newer version of MPICH. Halim www.mcs.anl.gov/~aamer On 9/21/18 10:39 AM, Alexander Rast wrote: > All, > > I'm running an MPI_Comm_accept in a separate thread whose purpose is to > allow connections from other (hitherto unknown) MPI universes. A > well-known issue of such configurations is that MPI_Comm_accept being > blocking, in order for the application to exit, a connection MUST be > made even if no actual other universes attempted to connect. In this > situation (see Gropp, et al. "Using Advanced MPI", section 6.5) it seems > the 'customary' solution is to have the local universe connect to itself > and then shut down. > > However, I'm getting the following error on exit: > > Fatal error in PMPI_Comm_accept: Message truncated, error stack: > PMPI_Comm_accept(129).............: > MPI_Comm_accept(port="tag#0$description#aesop.cl.cam.ac.uk > <http://aesop.cl.cam.ac.uk>$port#43337$ifname#128.232.98.176$", > MPI_INFO_NULL, root=6, MPI_COMM_WORLD, newcomm=0x1473f24) failed > MPID_Comm_accept(153).............: > MPIDI_Comm_accept(1005)...........: > MPIR_Bcast_intra(1249)............: > MPIR_SMP_Bcast(1088)..............: > MPIR_Bcast_binomial(239)..........: > MPIDI_CH3U_Receive_data_found(131): Message from rank 0 and tag 2 > truncated; 260 bytes received but buffer size is 12 > > You typically get several of these messages, the number seems to vary > from trial to trial, I'm guessing it comes from different MPI processes > (although there is no fixed relationship between number of processes > started and number of error messages) > > Does anyone have any suggestions on what types of problems might cause > this error? (I'm not expecting you to identify and debug the problem > specifically, unless, perhaps, this error is indicative of some > particular mistake, just would like any hints on where to look) > > If it helps, here are the 3 main relevant functions involved - there is, > of course, a lot more going on in the application besides these, but the > error is occurring at shutdown and by this point the rest of the > application is quiescent. Also note that the Connect routine is NOT > called at shutdown; it's invoked when a 'real' universe wants to connect. > > //------------------------------------------------------------------------------ > > void* CommonBase::Accept(void* par) > /* Blocking routine to connect to another MPI universe by publishing a port. > This operates in a separate thread to avoid blocking the whole process. > */ > { > CommonBase* parent=static_cast<CommonBase*>(par); > > while (parent->AcceptConns.load(std::memory_order_relaxed)) > { > // run the blocking accept itself. > if > (MPI_Comm_accept(parent->MPIPort.load(std::memory_order_seq_cst),MPI_INFO_NULL,parent->Lrank.load(std::memory_order_relaxed),MPI_COMM_WORLD,parent->Tcomm.load(std::memory_order_seq_cst))) > { > printf("Error: attempt to connect to another MPI universe failed\n"); > parent->AcceptConns.store(false,std::memory_order_relaxed); > break; > } > // Now trigger the Connect process in the main thread to complete the setup > PMsg_p Creq; > string N(""); // zero-length string indicates a server-side > connection > Creq.Put(0,&N); > Creq.Key(Q::SYST,Q::CONN); > Creq.Src(0); > Creq.comm = MPI_COMM_SELF; > Creq.Send(0); > while (*(parent->Tcomm.load(std::memory_order_seq_cst)) != > MPI_COMM_NULL); // block until connect has succeeded > } > pthread_exit(par); > return par; > } > > //------------------------------------------------------------------------------ > > unsigned CommonBase::Connect(string svc) > // connects this process' MPI universe to a remote universe that has > published > // a name to access it by. > { > int error = MPI_SUCCESS; > // a server has its port already so can just open a comm > if (svc=="") Comms.push_back(*Tcomm.load(std::memory_order_seq_cst)); > else // clients need to look up the service name > { > MPI_Comm newcomm; > char port[MPI_MAX_PORT_NAME]; > // Get the published port for the service name asked for. > // Exit if we don't get a port, probably because the remote universe > isn't > // initialised yet (we can always retry). > if (error = MPI_Lookup_name(svc.c_str(),MPI_INFO_NULL,port)) return > error; > // now try to establish the connection itself. Again, we can always > retry. > if (error = > MPI_Comm_connect(port,MPI_INFO_NULL,0,MPI_COMM_WORLD,&newcomm)) return > error; > Comms.push_back(newcomm); // as long as we succeeded, add to the list > of comms > } > int rUsize; > MPI_Comm_remote_size(Comms.back(), &rUsize); > Usize.push_back(rUsize); // record the size of the remote universe > FnMapx.push_back(new FnMap_t); // give the new comm some function tables > to use > pPmap.push_back(new ProcMap(this)); // and a new processor map for the > remote group > PMsg_p prMsg; > SendPMap(Comms.back(), &prMsg); // Send our process data to the > remote group > int fIdx=FnMapx.size()-1; > // populate the new function table with the global functions > (*FnMapx[fIdx])[Msg_p::KEY(Q::EXIT )] = &CommonBase::OnExit; > (*FnMapx[fIdx])[Msg_p::KEY(Q::PMAP )] = &CommonBase::OnPmap; > (*FnMapx[fIdx])[Msg_p::KEY(Q::SYST,Q::PING,Q::ACK )] = > &CommonBase::OnSystPingAck; > (*FnMapx[fIdx])[Msg_p::KEY(Q::SYST,Q::PING,Q::REQ )] = > &CommonBase::OnSystPingReq; > (*FnMapx[fIdx])[Msg_p::KEY(Q::TEST,Q::FLOO )] = > &CommonBase::OnTestFloo; > if (svc=="") *Tcomm.load(std::memory_order_seq_cst) = MPI_COMM_NULL; // > release any Accept comm. > return error; > } > > //------------------------------------------------------------------------------ > > unsigned CommonBase::OnExit(PMsg_p * Z,unsigned cIdx) > // Do not post anything further here - the LogServer may have already gone > { > AcceptConns.store(false,std::memory_order_relaxed); // stop accepting > connections > if (acpt_running) > { > printf("(%s)::CommonBase::OnExit closing down Accept MPI > request\n",Sderived.c_str()); > fflush(stdout); > // have to close the Accept thread via a matching MPI_Comm_connect > // because the MPI interface has made no provision for a nonblocking > accept, thus > // otherwise the Accept thread will block forever waiting for a > message that will > // never come because we are shutting down. See Gropp, et al. "Using > Advanced MPI" > MPI_Comm dcomm; > > MPI_Comm_connect(MPIPort.load(std::memory_order_seq_cst),MPI_INFO_NULL,Lrank.load(std::memory_order_relaxed),MPI_COMM_WORLD,&dcomm); > pthread_join(MPI_accept,NULL); > acpt_running = false; > } > if (Urank == Lrank.load(std::memory_order_relaxed)) > { > > MPI_Unpublish_name(MPISvc,MPI_INFO_NULL,MPIPort.load(std::memory_order_seq_cst)); > MPI_Close_port(MPIPort.load(std::memory_order_seq_cst)); > } > return 1; > } > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] couldn't built mpich-master on SuSE Linux with Sun C
by Siegmar Gross 27 Sep '18

27 Sep '18

Hi Giuseppe, I'll do next week. At the moment I'm not in my office and I have no access to my machine. Best regards Siegmar Von meinem Handy gesendet. -------- Ursprüngliche Nachricht --------Von: "Congiu, Giuseppe" <gcongiu(a)anl.gov> Datum: 26.09.18 21:41 (GMT+01:00) An: discuss(a)mpich.org Betreff: Re: [mpich-discuss] couldn't built mpich-master on SuSE Linux with Sun C Hi Siegmar, I have tried replicating the linking problem using the configure options you provided. I have used Oracle Developer Studio 12.3. Mpich master “701bc7e5f84467188dcdc1ff585349e994a9990a". Compilation worked fine for me. Can you attach your config.log file so I can have a look at it? Moreover, can you recompile Mpich with "make V=1" and attach the corresponding output as well? Thank you, Giuseppe > On Jun 6, 2018, at 6:21 AM, Siegmar Gross <siegmar.gross(a)informatik.hs-fulda.de> wrote: > > Hi, > > I tried to build mpich-master on my "SUSE Linux Enterprise Server 12.3 > (x86_64)" with Sun C 5.15 (Oracle Developer Studio 12.6). Unfortunately, > I get the following error, that I already reported already on May 9th. > > > loki mpich-master_2018-06-06_Linux.x86_64.64_cc 122 tail -22 log.make.Linux.x86_64.64_cc | grep -v NOTICE > "../mpich/src/include/mpir_handlemem.h", line 61: warning: null dimension: indirect > "../mpich/src/include/mpir_handlemem.h", line 122: warning: null dimension: indirect > MOD src/binding/fortran/use_mpi/mpi.mod-stamp > "./src/include/mpichconf.h", line 1708: Warning (Anachronism): Attempt to redefine __restrict__ without using #undef. > 1 Warning(s) detected. > f90: Warning: Option -shared passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option --whole-archive passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option --no-whole-archive passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option -soname passed to ld, if ld is invoked, ignored otherwise > /usr/bin/ld: -r and -shared may not be used together > postopt: error: ld failed to link the binary > Makefile:16787: recipe for target 'lib/libmpi.la' failed > make[2]: *** [lib/libmpi.la] Error 2 > make[2]: Leaving directory '/export2/src/mpich-master/mpich-master_2018-06-06_Linux.x86_64.64_cc' > Makefile:39797: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/export2/src/mpich-master/mpich-master_2018-06-06_Linux.x86_64.64_cc' > Makefile:10453: recipe for target 'all' failed > make: *** [all] Error 2 > loki mpich-master_2018-06-06_Linux.x86_64.64_cc 123 > > > I used the following commands to update and configure MPICH. > > cd mpich > git pull https://github.com/pmodels/mpich.git master > git submodule update --init --recursive > autogen.sh > > mkdir mpich-master_`date -I'date'`_${SYSTEM_ENV}.${MACHINE_ENV}.64_cc > cd mpich-master_`date -I'date'`_${SYSTEM_ENV}.${MACHINE_ENV}.64_cc > > ../mpich/configure \ > --prefix=/usr/local/mpich-master_64_cc \ > --libdir=/usr/local/mpich-master_64_cc/lib64 \ > --includedir=/usr/local/mpich-master_64_cc/include64 \ > CC="cc" CXX="CC" F77="f77" FC="f95" \ > CFLAGS="-m64" CXXFLAGS="-m64" FFLAGS="-m64" FCFLAGS="-m64" \ > LDFLAGS="-m64 -L/usr/lib64 -R/usr/lib64" \ > --enable-fortran=yes --enable-cxx --enable-romio \ > --enable-debuginfo --enable-smpcoll \ > --enable-threads=multiple --with-thread-package=posix \ > --enable-shared \ > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_cc > > make -j 6 |& tee log.make.$SYSTEM_ENV.$MACHINE_ENV.64_cc > > > I would be grateful, if somebody can fix the problem or is it a problem of the > Oracle compiler?. Do you need anything else? Thank you very much for any help > in advance. > > > Kind regards > > Siegmar > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] couldn't built mpich-master on SuSE Linux with Sun C
by Congiu, Giuseppe 26 Sep '18

26 Sep '18

Hi Siegmar, I have tried replicating the linking problem using the configure options you provided. I have used Oracle Developer Studio 12.3. Mpich master “701bc7e5f84467188dcdc1ff585349e994a9990a". Compilation worked fine for me. Can you attach your config.log file so I can have a look at it? Moreover, can you recompile Mpich with "make V=1" and attach the corresponding output as well? Thank you, Giuseppe > On Jun 6, 2018, at 6:21 AM, Siegmar Gross <siegmar.gross(a)informatik.hs-fulda.de> wrote: > > Hi, > > I tried to build mpich-master on my "SUSE Linux Enterprise Server 12.3 > (x86_64)" with Sun C 5.15 (Oracle Developer Studio 12.6). Unfortunately, > I get the following error, that I already reported already on May 9th. > > > loki mpich-master_2018-06-06_Linux.x86_64.64_cc 122 tail -22 log.make.Linux.x86_64.64_cc | grep -v NOTICE > "../mpich/src/include/mpir_handlemem.h", line 61: warning: null dimension: indirect > "../mpich/src/include/mpir_handlemem.h", line 122: warning: null dimension: indirect > MOD src/binding/fortran/use_mpi/mpi.mod-stamp > "./src/include/mpichconf.h", line 1708: Warning (Anachronism): Attempt to redefine __restrict__ without using #undef. > 1 Warning(s) detected. > f90: Warning: Option -shared passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option --whole-archive passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option --no-whole-archive passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise > f90: Warning: Option -soname passed to ld, if ld is invoked, ignored otherwise > /usr/bin/ld: -r and -shared may not be used together > postopt: error: ld failed to link the binary > Makefile:16787: recipe for target 'lib/libmpi.la' failed > make[2]: *** [lib/libmpi.la] Error 2 > make[2]: Leaving directory '/export2/src/mpich-master/mpich-master_2018-06-06_Linux.x86_64.64_cc' > Makefile:39797: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/export2/src/mpich-master/mpich-master_2018-06-06_Linux.x86_64.64_cc' > Makefile:10453: recipe for target 'all' failed > make: *** [all] Error 2 > loki mpich-master_2018-06-06_Linux.x86_64.64_cc 123 > > > I used the following commands to update and configure MPICH. > > cd mpich > git pull https://github.com/pmodels/mpich.git master > git submodule update --init --recursive > autogen.sh > > mkdir mpich-master_`date -I'date'`_${SYSTEM_ENV}.${MACHINE_ENV}.64_cc > cd mpich-master_`date -I'date'`_${SYSTEM_ENV}.${MACHINE_ENV}.64_cc > > ../mpich/configure \ > --prefix=/usr/local/mpich-master_64_cc \ > --libdir=/usr/local/mpich-master_64_cc/lib64 \ > --includedir=/usr/local/mpich-master_64_cc/include64 \ > CC="cc" CXX="CC" F77="f77" FC="f95" \ > CFLAGS="-m64" CXXFLAGS="-m64" FFLAGS="-m64" FCFLAGS="-m64" \ > LDFLAGS="-m64 -L/usr/lib64 -R/usr/lib64" \ > --enable-fortran=yes --enable-cxx --enable-romio \ > --enable-debuginfo --enable-smpcoll \ > --enable-threads=multiple --with-thread-package=posix \ > --enable-shared \ > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_cc > > make -j 6 |& tee log.make.$SYSTEM_ENV.$MACHINE_ENV.64_cc > > > I would be grateful, if somebody can fix the problem or is it a problem of the > Oracle compiler?. Do you need anything else? Thank you very much for any help > in advance. > > > Kind regards > > Siegmar > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0