June 2017 - discuss - mailman3.cels.anl.gov

-genvexcl
by Faraj, Daniel 14 Jun '17

14 Jun '17

Dear MPICH folks, Flavors of MPI implementations support methods to allow or suppress mpirun from propagating environment variables to hosts in the MPI job. MPICH 2.3 does have similar options however it does not seem to have the –genvexcl option to exclude certain environment variables from propagating. Is there a way to do so? -Daniel _______________________________________________ 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] Strange, inconsistent behaviour with MPI_Comm_spawn
by Alexander Rast 14 Jun '17

14 Jun '17

Still more conjecture on my part, I think I understand what's going on with the gethostbyname failed message, but have no idea how one would go about fixing it. The exact message gives 'gethostbyname failed, pi@Burns (errno 1)'. I think this is a case of the underlying implementation not being intelligent enough to strip the username off in order to resolve the host address. In other words, it's looking for a host named 'pi@Burns' rather than a host Burns to which it's going to authenticate as user pi. If you try to use the hostname without user this fails, because then it tries to authenticate using the current username from the shell that invoked mpiexec (in my case on what will eventually become a 'root host' machine - an ordinary Ubuntu desktop PC) which fails because on the other MPI hosts that username doesn't exist. I have authentication set up using RSA keys which authenticates the local user on the 'root host' desktop PC into the 'working user' on the remote MPI hosts, but it seems the MPI_Comm_spawn function isn't using that authentication path. What it looks like, is that the MPICH implementation may be such that in order to run MPI_Comm_spawn you have to have an identical username on each host you hope to spawn a process on. I very much *hope* this isn't the case, because this would be exceptionally awkward, it would mean that for each different user wanting to run MPI jobs on the remote cluster they'd have to have their own private user and directory on each node in the cluster. So 1) is it possible to and 2) how would I, configure the MPI_Comm_spawn command or associated hosts so that you can authenticate as user X on host Y (X@Y) for each spawn host using authorized keys from your user W on machine Z, i.e. on machine Y you have in directory /home/X/.ssh/authorized_keys an entry for W@Z? On Tue, Jun 13, 2017 at 5:15 PM, Alexander Rast < alex.rast.technical(a)gmail.com> wrote: > OK, some progress. After more work I determined that the bulk of the truly > bizarre inconsistencies was down to obnoxious, intrusive behaviour in > Ubuntu of gnome-keyring-daemon, for example see the following post: > > https://askubuntu.com/questions/564821/why-cant-i- > interact-with-my-ssh-agent-e-g-ssh-add-d-doesnt-work > > which by the way has not been fixed as of 16.04 Ubuntu. > > It seems gnome-keyring-daemon is a particularly badly-behaved utility and > doesn't help itself with multiple autoload attempts at Ubuntu startup. You > don't know what ssh agent is actually loaded and which RSA keys it has > cached. It's also apparently very difficult to get rid of, although there > are ways. I got it eventually to stop loading itself. (Perhaps the MPI > community might whinge to Ubuntu about this behaviour? Many people have > complained about the antisocial behaviour of gnome-keyring-daemon but so > far Ubuntu's response has been: 'we can't see why this should be considered > a problem. And we have doubts about what you're trying to achieve') > > So now the problem has got to the point where there are 2 alternative > error responses, both occurring at the MPI_Comm_spawn command. I've > included typical error outputs for both scenarios, using the code posted > earlier. The 2 errors occur with slightly different versions of the > configuration file used to spawn the processes, which I'm also including. > Obviously _2 files go together. > > Any thoughts now on what might be causing either of these 2 problems? I > find the gethostbyname failed messages particularly perplexing, since I'm > able to ssh into the machines themselves without difficulty either by name > or IP address. > > On Fri, Jun 9, 2017 at 1:53 PM, Alexander Rast < > alex.rast.technical(a)gmail.com> wrote: > >> I've reached a limit of mystification. Attempting to run an MPI >> application using MPI_Comm_spawn from a host is resulting in bizarre, >> inconsistent behaviour of ssh and ssh-askpass. >> >> What I did is, I created an RSA keypair using ssh-keygen, copied the >> public keys into the ./ssh directories on the machines I'll be running MPI >> on, put them in the authorized_keys file, placed all the machines in the >> known_hosts file on the launcher host (which is starting MPI_Comm_spawn), >> then ran eval ssh-agent and added the id_rsa file to the agent on the >> launcher host. >> >> You can verify that this part of the system is working because I can use >> ssh directly to access the worker machines that will be running the >> application. >> >> But when I actually try to run the MPI application, when it gets to the >> spawn, all sorts of wierd and wild stuff happens. Sometimes a dialogue >> (which aggressively grabs focus) comes up asking for a password (OpenSSH >> Authentication). Other times the same program has just said that the >> identity/authenticity of the target machine can't be established - do I >> want to continue? (A yes causes authentication to fail). In still other >> cases, it appeared to open the connection but then MPI crashed saying it >> couldn't get the host by name. (yes, every machine has the hostnames of >> every other machine in its hosts file). And in yet another case, it seemed >> to try to run but then crashed saying unexpected end-of-file. And so on. >> There seems to be no rhyme or reason to the errors, I can't reproduce >> anything, each time I try it some new and surprising behaviour comes up. >> What's happening? Do I have to do something unusual with machine >> configuration/environment? >> >> Here are the associated MPI files if anyone wants to look for errors. In >> fact there are probably some errors in the code itself, because it's never >> been able to be debugged (because of this wierd behaviour) but I am fairly >> sure at least the sequence through to the spawn command is OK. All help >> appreciated... >> > > _______________________________________________ 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] Strange, inconsistent behaviour with MPI_Comm_spawn
by Alexander Rast 13 Jun '17

13 Jun '17

OK, some progress. After more work I determined that the bulk of the truly bizarre inconsistencies was down to obnoxious, intrusive behaviour in Ubuntu of gnome-keyring-daemon, for example see the following post: https://askubuntu.com/questions/564821/why-cant-i-interact-with-my-ssh-agen… which by the way has not been fixed as of 16.04 Ubuntu. It seems gnome-keyring-daemon is a particularly badly-behaved utility and doesn't help itself with multiple autoload attempts at Ubuntu startup. You don't know what ssh agent is actually loaded and which RSA keys it has cached. It's also apparently very difficult to get rid of, although there are ways. I got it eventually to stop loading itself. (Perhaps the MPI community might whinge to Ubuntu about this behaviour? Many people have complained about the antisocial behaviour of gnome-keyring-daemon but so far Ubuntu's response has been: 'we can't see why this should be considered a problem. And we have doubts about what you're trying to achieve') So now the problem has got to the point where there are 2 alternative error responses, both occurring at the MPI_Comm_spawn command. I've included typical error outputs for both scenarios, using the code posted earlier. The 2 errors occur with slightly different versions of the configuration file used to spawn the processes, which I'm also including. Obviously _2 files go together. Any thoughts now on what might be causing either of these 2 problems? I find the gethostbyname failed messages particularly perplexing, since I'm able to ssh into the machines themselves without difficulty either by name or IP address. On Fri, Jun 9, 2017 at 1:53 PM, Alexander Rast < alex.rast.technical(a)gmail.com> wrote: > I've reached a limit of mystification. Attempting to run an MPI > application using MPI_Comm_spawn from a host is resulting in bizarre, > inconsistent behaviour of ssh and ssh-askpass. > > What I did is, I created an RSA keypair using ssh-keygen, copied the > public keys into the ./ssh directories on the machines I'll be running MPI > on, put them in the authorized_keys file, placed all the machines in the > known_hosts file on the launcher host (which is starting MPI_Comm_spawn), > then ran eval ssh-agent and added the id_rsa file to the agent on the > launcher host. > > You can verify that this part of the system is working because I can use > ssh directly to access the worker machines that will be running the > application. > > But when I actually try to run the MPI application, when it gets to the > spawn, all sorts of wierd and wild stuff happens. Sometimes a dialogue > (which aggressively grabs focus) comes up asking for a password (OpenSSH > Authentication). Other times the same program has just said that the > identity/authenticity of the target machine can't be established - do I > want to continue? (A yes causes authentication to fail). In still other > cases, it appeared to open the connection but then MPI crashed saying it > couldn't get the host by name. (yes, every machine has the hostnames of > every other machine in its hosts file). And in yet another case, it seemed > to try to run but then crashed saying unexpected end-of-file. And so on. > There seems to be no rhyme or reason to the errors, I can't reproduce > anything, each time I try it some new and surprising behaviour comes up. > What's happening? Do I have to do something unusual with machine > configuration/environment? > > Here are the associated MPI files if anyone wants to look for errors. In > fact there are probably some errors in the code itself, because it's never > been able to be debugged (because of this wierd behaviour) but I am fairly > sure at least the sequence through to the spawn command is OK. All help > appreciated... > _______________________________________________ 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] -configfile size limit?
by Kenneth Raffenetti 12 Jun '17

12 Jun '17

Hi Jeff, It would probably be fastest if you could send me a copy of your config file off list so I can trigger the failure locally and work backwards. Ken On 06/09/2017 03:43 PM, Daily, Jeff A wrote: > I have been using mpiexec.hydra for launching non-MPI applications that > communicate via ZeroMQ. I use the configfile parameter, one line per > application. Here’s an example: > > -n 1 -env FNCS_BROKER tcp://*:5570 fncs_broker 10 > > -n 1 -wdir R1_12_47_1_feeder_6 gridlabd R1_12_47_1_feeder_6.glm > > -n 1 -wdir R1_12_47_1_feeder_7 gridlabd R1_12_47_1_feeder_7.glm > > -n 1 -wdir R1_12_47_2_feeder_0 gridlabd R1_12_47_2_feeder_0.glm > > -n 1 -wdir R1_12_47_2_feeder_1 gridlabd R1_12_47_2_feeder_1.glm > > -n 1 -wdir R1_12_47_2_feeder_2 gridlabd R1_12_47_2_feeder_2.glm > > -n 1 -wdir R1_12_47_3_feeder_4 gridlabd R1_12_47_3_feeder_4.glm > > -n 1 -wdir R1_12_47_3_feeder_5 gridlabd R1_12_47_3_feeder_5.glm > > -n 1 -wdir R1_12_47_4_feeder_8 gridlabd R1_12_47_4_feeder_8.glm > > -n 1 -wdir R1_25_00_1_feeder_3 gridlabd R1_25_00_1_feeder_3.glm > > -n 1 -wdir matpower ./start_MATPOWER case9.m real_power_demand.txt 18000 > 3600 > > This worked well for this smaller case. I then tried a case with 15002 > lines in my configfile, but I got a backtrace from mpiexec > > *** glibc detected *** mpiexec: free(): invalid pointer: > 0x0000000000736b10 *** > > I’m guessing there is some size limit for the configfile? Can anyone > confirm and suggest a patch? > > Jeff > > > > _______________________________________________ > 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

-configfile size limit?
by Daily, Jeff A 09 Jun '17

09 Jun '17

I have been using mpiexec.hydra for launching non-MPI applications that communicate via ZeroMQ. I use the configfile parameter, one line per application. Here’s an example: -n 1 -env FNCS_BROKER tcp://*:5570 fncs_broker 10 -n 1 -wdir R1_12_47_1_feeder_6 gridlabd R1_12_47_1_feeder_6.glm -n 1 -wdir R1_12_47_1_feeder_7 gridlabd R1_12_47_1_feeder_7.glm -n 1 -wdir R1_12_47_2_feeder_0 gridlabd R1_12_47_2_feeder_0.glm -n 1 -wdir R1_12_47_2_feeder_1 gridlabd R1_12_47_2_feeder_1.glm -n 1 -wdir R1_12_47_2_feeder_2 gridlabd R1_12_47_2_feeder_2.glm -n 1 -wdir R1_12_47_3_feeder_4 gridlabd R1_12_47_3_feeder_4.glm -n 1 -wdir R1_12_47_3_feeder_5 gridlabd R1_12_47_3_feeder_5.glm -n 1 -wdir R1_12_47_4_feeder_8 gridlabd R1_12_47_4_feeder_8.glm -n 1 -wdir R1_25_00_1_feeder_3 gridlabd R1_25_00_1_feeder_3.glm -n 1 -wdir matpower ./start_MATPOWER case9.m real_power_demand.txt 18000 3600 This worked well for this smaller case. I then tried a case with 15002 lines in my configfile, but I got a backtrace from mpiexec *** glibc detected *** mpiexec: free(): invalid pointer: 0x0000000000736b10 *** I’m guessing there is some size limit for the configfile? Can anyone confirm and suggest a patch? Jeff _______________________________________________ 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] Strange, inconsistent behaviour with MPI_Comm_spawn
by Reuti 09 Jun '17

09 Jun '17

Hi, to avoid any additional password/-phrase requests, it might be better to set up hostbased authentication and remove the public key from the authorized_keys file again to check whether it's working. This should be set up to work also between slave nodes for Hydra. https://arc.liv.ac.uk/SGE/howto/hostbased-ssh.html -- Reuti > Am 09.06.2017 um 14:53 schrieb Alexander Rast <alex.rast.technical(a)gmail.com>: > > I've reached a limit of mystification. Attempting to run an MPI application using MPI_Comm_spawn from a host is resulting in bizarre, inconsistent behaviour of ssh and ssh-askpass. > > What I did is, I created an RSA keypair using ssh-keygen, copied the public keys into the ./ssh directories on the machines I'll be running MPI on, put them in the authorized_keys file, placed all the machines in the known_hosts file on the launcher host (which is starting MPI_Comm_spawn), then ran eval ssh-agent and added the id_rsa file to the agent on the launcher host. > > You can verify that this part of the system is working because I can use ssh directly to access the worker machines that will be running the application. > > But when I actually try to run the MPI application, when it gets to the spawn, all sorts of wierd and wild stuff happens. Sometimes a dialogue (which aggressively grabs focus) comes up asking for a password (OpenSSH Authentication). Other times the same program has just said that the identity/authenticity of the target machine can't be established - do I want to continue? (A yes causes authentication to fail). In still other cases, it appeared to open the connection but then MPI crashed saying it couldn't get the host by name. (yes, every machine has the hostnames of every other machine in its hosts file). And in yet another case, it seemed to try to run but then crashed saying unexpected end-of-file. And so on. There seems to be no rhyme or reason to the errors, I can't reproduce anything, each time I try it some new and surprising behaviour comes up. What's happening? Do I have to do something unusual with machine configuration/environment? > > Here are the associated MPI files if anyone wants to look for errors. In fact there are probably some errors in the code itself, because it's never been able to be debugged (because of this wierd behaviour) but I am fairly sure at least the sequence through to the spawn command is OK. All help appreciated... > <Dynamic_Procs.tar.gz> > _______________________________________________ > 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

Strange, inconsistent behaviour with MPI_Comm_spawn
by Alexander Rast 09 Jun '17

09 Jun '17

I've reached a limit of mystification. Attempting to run an MPI application using MPI_Comm_spawn from a host is resulting in bizarre, inconsistent behaviour of ssh and ssh-askpass. What I did is, I created an RSA keypair using ssh-keygen, copied the public keys into the ./ssh directories on the machines I'll be running MPI on, put them in the authorized_keys file, placed all the machines in the known_hosts file on the launcher host (which is starting MPI_Comm_spawn), then ran eval ssh-agent and added the id_rsa file to the agent on the launcher host. You can verify that this part of the system is working because I can use ssh directly to access the worker machines that will be running the application. But when I actually try to run the MPI application, when it gets to the spawn, all sorts of wierd and wild stuff happens. Sometimes a dialogue (which aggressively grabs focus) comes up asking for a password (OpenSSH Authentication). Other times the same program has just said that the identity/authenticity of the target machine can't be established - do I want to continue? (A yes causes authentication to fail). In still other cases, it appeared to open the connection but then MPI crashed saying it couldn't get the host by name. (yes, every machine has the hostnames of every other machine in its hosts file). And in yet another case, it seemed to try to run but then crashed saying unexpected end-of-file. And so on. There seems to be no rhyme or reason to the errors, I can't reproduce anything, each time I try it some new and surprising behaviour comes up. What's happening? Do I have to do something unusual with machine configuration/environment? Here are the associated MPI files if anyone wants to look for errors. In fact there are probably some errors in the code itself, because it's never been able to be debugged (because of this wierd behaviour) but I am fairly sure at least the sequence through to the spawn command is OK. All help appreciated... _______________________________________________ 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] About error in mpio.h with mpicc
by Halim Amer 07 Jun '17

07 Jun '17

Doesn't Composer XE come with Intel MPI? I suggest using it if possible. If you really want to use MPICH, then I suggest that you grab a more recent 3.2 tarball, which can be found at http://www.mpich.org/downloads. The version you are using is outdated. If you are still seeing the same problem with the recent MPICH tarball, please let us know. Halim www.mcs.anl.gov/~aamer On 6/7/17 1:06 AM, Igor R. Shein wrote: > Dear colleagues, in compiling a program I have a problem with compiling. > > I use Intel composer_xe_2013 + MKL and mpich2-1.4.1p1. > > > > > > +++++++++++++++++++++++++++++++++++++++ > > MKLPATH=$(MKLROOT)/lib/intel64 > > MKL_FFTW_PATH=$(MKLROOT)/interfaces/fftw3xf/ > > MKLINCLUDE=$(MKLROOT)/include > > > > FCOMPILER = mpif90 > > F90COMPILER = mpif90 > > FCOMPILERFLAGS = -O3 > > FCPPFLAGS = -DMPI -DNOMPIMOD > > FORTRANLIBS = -lifcore -lsvml -lirc -limf -lifport > > > > #C: > > CCOMPILER = mpicc > > CCOMPILERFLAGS = -O2 -fno-gnu-keywords > > #CCOMPILERFLAGS = -g -O0 > > CPPFLAGS = -DF_APPENDS_UNDERSCORE=0 -DMPI > > > > #LIBRARIES AND INCLUDE DIRECTORIES > > LAPACKLIB = > > BLASLIB = -L${MKLPATH} -I${MKLINCLUDE} -Wl,--start-group -mkl=sequential > -Wl,--end-group -lpthread > > FFTWLIB = $(MKL_FFTW_PATH)/libfftw3xf_intel.a > > > > EXTRALIBS = -lmpi -lmpich > > INCLUDEDIRS = -I/opt/intel/mkl/include/fftw > > ++++++++++++++++++++++++++++++++++++++++ > > but.....there is a strange error: > > ++++++++++++++++++++++++++++++++++++++++ > > mpicc -O2 -fno-gnu-keywords -I./include -I../../include > -I/opt/intel/mkl/include/fftw -DF_APPENDS_UNDERSCORE=0 -DMPI -c -o bases.o > bases.c > > mpicc -O2 -fno-gnu-keywords -I./include -I../../include > -I/opt/intel/mkl/include/fftw -DF_APPENDS_UNDERSCORE=0 -DMPI -c -o > basesInterstitial.o basesInterstitial.c > > In file included from /usr/local/include/mpi.h(1184), > > from basesInterstitial.c(29): > > /usr/local/include/mpio.h(142): error: expected a "{" > > MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5); > > ^ > > > > In file included from basesInterstitial.c(30): > > ./include/mpicom.h(8): warning #12: parsing restarts here after previous > syntax error > > extern struct { > > ^ > > > > In file included from basesInterstitial.c(30): > > ./include/mpicom.h(12): warning #77: this declaration has no storage class > or type specifier > > } mpicom0_; > > ^ > > > > basesInterstitial.c(922): error: identifier "intrak_mpirank" is undefined > > mpirank = intrak_mpirank; > > ^ > > > > basesInterstitial.c(923): error: identifier "intrak_mpisize" is undefined > > mpisize = intrak_mpisize; > > ^ > > > > basesInterstitial.c(924): error: identifier "intrak_comm" is undefined > > mycomm = MPI_Comm_f2c(intrak_comm); > > ^ > > > > basesInterstitial.c(1246): error: identifier "intrak_mpirank" is undefined > > mpirank = intrak_mpirank; > > ^ > > > > basesInterstitial.c(1247): error: identifier "intrak_mpisize" is undefined > > mpisize = intrak_mpisize; > > ^ > > > > basesInterstitial.c(1248): error: identifier "intrak_comm" is undefined > > mycomm = MPI_Comm_f2c(intrak_comm); > > ^ > > +++++++++++++++++++++++++++++++++++++++++++ > > > > I would be very grateful for your help > > > > --- > Это сообщение проверено на вирусы антивирусом Avast. > https://www.avast.com/antivirus > > > > _______________________________________________ > 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] About error in mpio.h with mpicc
by Min Si 07 Jun '17

07 Jun '17

Hi, MPICH2-1.4 is a very old version. Could you please try the latest release ? You can download it from this website. http://www.mpich.org/downloads/ Min On 6/7/17 1:06 AM, Igor R. Shein wrote: > > Dear colleagues, in compiling a program I have a problem with compiling. > > I use Intel composer_xe_2013 + MKL and mpich2-1.4.1p1. > > +++++++++++++++++++++++++++++++++++++++ > > MKLPATH=$(MKLROOT)/lib/intel64 > > MKL_FFTW_PATH=$(MKLROOT)/interfaces/fftw3xf/ > > MKLINCLUDE=$(MKLROOT)/include > > FCOMPILER = mpif90 > > F90COMPILER = mpif90 > > FCOMPILERFLAGS = -O3 > > FCPPFLAGS = -DMPI -DNOMPIMOD > > FORTRANLIBS = -lifcore -lsvml -lirc -limf -lifport > > #C: > > CCOMPILER = mpicc > > CCOMPILERFLAGS = -O2 -fno-gnu-keywords > > #CCOMPILERFLAGS = -g -O0 > > CPPFLAGS = -DF_APPENDS_UNDERSCORE=0 -DMPI > > #LIBRARIES AND INCLUDE DIRECTORIES > > LAPACKLIB = > > BLASLIB = -L${MKLPATH} -I${MKLINCLUDE} -Wl,--start-group > -mkl=sequential -Wl,--end-group -lpthread > > FFTWLIB = $(MKL_FFTW_PATH)/libfftw3xf_intel.a > > EXTRALIBS = -lmpi -lmpich > > INCLUDEDIRS = -I/opt/intel/mkl/include/fftw > > ++++++++++++++++++++++++++++++++++++++++ > > but.....there is a strange error: > > ++++++++++++++++++++++++++++++++++++++++ > > mpicc -O2 -fno-gnu-keywords -I./include -I../../include > -I/opt/intel/mkl/include/fftw -DF_APPENDS_UNDERSCORE=0 -DMPI -c -o > bases.o bases.c > > mpicc -O2 -fno-gnu-keywords -I./include -I../../include > -I/opt/intel/mkl/include/fftw -DF_APPENDS_UNDERSCORE=0 -DMPI -c -o > basesInterstitial.o basesInterstitial.c > > In file included from /usr/local/include/mpi.h(1184), > > from basesInterstitial.c(29): > > /usr/local/include/mpio.h(142): error: expected a "{" > > MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5); > > ^ > > In file included from basesInterstitial.c(30): > > ./include/mpicom.h(8): warning #12: parsing restarts here after > previous syntax error > > extern struct { > > ^ > > In file included from basesInterstitial.c(30): > > ./include/mpicom.h(12): warning #77: this declaration has no storage > class or type specifier > > } mpicom0_; > > ^ > > basesInterstitial.c(922): error: identifier "intrak_mpirank" is undefined > > mpirank = intrak_mpirank; > > ^ > > basesInterstitial.c(923): error: identifier "intrak_mpisize" is undefined > > mpisize = intrak_mpisize; > > ^ > > basesInterstitial.c(924): error: identifier "intrak_comm" is undefined > > mycomm = MPI_Comm_f2c(intrak_comm); > > ^ > > basesInterstitial.c(1246): error: identifier "intrak_mpirank" is undefined > > mpirank = intrak_mpirank; > > ^ > > basesInterstitial.c(1247): error: identifier "intrak_mpisize" is undefined > > mpisize = intrak_mpisize; > > ^ > > basesInterstitial.c(1248): error: identifier "intrak_comm" is undefined > > mycomm = MPI_Comm_f2c(intrak_comm); > > ^ > > +++++++++++++++++++++++++++++++++++++++++++ > > I would be very grateful for your help > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Без вирусов. www.avast.ru > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > _______________________________________________ > 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

About error in mpio.h with mpicc
by Igor R. Shein 07 Jun '17

07 Jun '17

Dear colleagues, in compiling a program I have a problem with compiling. I use Intel composer_xe_2013 + MKL and mpich2-1.4.1p1. +++++++++++++++++++++++++++++++++++++++ MKLPATH=$(MKLROOT)/lib/intel64 MKL_FFTW_PATH=$(MKLROOT)/interfaces/fftw3xf/ MKLINCLUDE=$(MKLROOT)/include FCOMPILER = mpif90 F90COMPILER = mpif90 FCOMPILERFLAGS = -O3 FCPPFLAGS = -DMPI -DNOMPIMOD FORTRANLIBS = -lifcore -lsvml -lirc -limf -lifport #C: CCOMPILER = mpicc CCOMPILERFLAGS = -O2 -fno-gnu-keywords #CCOMPILERFLAGS = -g -O0 CPPFLAGS = -DF_APPENDS_UNDERSCORE=0 -DMPI #LIBRARIES AND INCLUDE DIRECTORIES LAPACKLIB = BLASLIB = -L${MKLPATH} -I${MKLINCLUDE} -Wl,--start-group -mkl=sequential -Wl,--end-group -lpthread FFTWLIB = $(MKL_FFTW_PATH)/libfftw3xf_intel.a EXTRALIBS = -lmpi -lmpich INCLUDEDIRS = -I/opt/intel/mkl/include/fftw ++++++++++++++++++++++++++++++++++++++++ but.....there is a strange error: ++++++++++++++++++++++++++++++++++++++++ mpicc -O2 -fno-gnu-keywords -I./include -I../../include -I/opt/intel/mkl/include/fftw -DF_APPENDS_UNDERSCORE=0 -DMPI -c -o bases.o bases.c mpicc -O2 -fno-gnu-keywords -I./include -I../../include -I/opt/intel/mkl/include/fftw -DF_APPENDS_UNDERSCORE=0 -DMPI -c -o basesInterstitial.o basesInterstitial.c In file included from /usr/local/include/mpi.h(1184), from basesInterstitial.c(29): /usr/local/include/mpio.h(142): error: expected a "{" MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5); ^ In file included from basesInterstitial.c(30): ./include/mpicom.h(8): warning #12: parsing restarts here after previous syntax error extern struct { ^ In file included from basesInterstitial.c(30): ./include/mpicom.h(12): warning #77: this declaration has no storage class or type specifier } mpicom0_; ^ basesInterstitial.c(922): error: identifier "intrak_mpirank" is undefined mpirank = intrak_mpirank; ^ basesInterstitial.c(923): error: identifier "intrak_mpisize" is undefined mpisize = intrak_mpisize; ^ basesInterstitial.c(924): error: identifier "intrak_comm" is undefined mycomm = MPI_Comm_f2c(intrak_comm); ^ basesInterstitial.c(1246): error: identifier "intrak_mpirank" is undefined mpirank = intrak_mpirank; ^ basesInterstitial.c(1247): error: identifier "intrak_mpisize" is undefined mpisize = intrak_mpisize; ^ basesInterstitial.c(1248): error: identifier "intrak_comm" is undefined mycomm = MPI_Comm_f2c(intrak_comm); ^ +++++++++++++++++++++++++++++++++++++++++++ I would be very grateful for your help --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0