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

Limitation of open files on Mira
by jt.meng＠siat.ac.cn 20 Apr '17

20 Apr '17

Hi Rob, Can we increase the number of open files on Mira to 1 million? Currently the number of open files is set to be 65536, and users can increase it manually to its hard limitation of 81920. Can we increase this hard limitation to 1 million for Mira for a one week test on MPI IO in Mira? Thanks. --------------- /etc/security/limits.conf--------------------------------- root soft nofile 65536 root hard nofile 81920 <-- Best, jt.meng(a)siat.ac.cn From: Latham, Robert J. Date: 2017-04-19 22:35 To: discuss(a)mpich.org Subject: Re: [mpich-discuss] Installation on Blue Gene/Q On Wed, 2017-04-19 at 13:58 +0200, pramod kumbhar wrote: > Hi Rob, > > Is this already installed/avaialble on MIRA? I would like to try this > to check some mpi i/o hints. Yes, there are several versions available: manual progress optimized: /projects/aurora_app/mpich3-ch4-ofi/install/gnu/bin auto progress optimized: /projects/aurora_app/mpich3-ch4-ofi/install-auto/gnu/bin manual progress debug: /projects/aurora_app/mpich3-ch4-ofi/install/gnu.debug/bin auto progress debug: /projects/aurora_app/mpich3-ch4-ofi/install-auto/gnu.debug/bin There are some performance considerations (both positive and negative) to consider: Current performance improvements versus [IBM's vendor-supplied MPICH]: 1.) Pt2pt latency - better than 2x speedup for small messages, large ones with few ranks-per-node less so due to detriment #2 listed below. 2.) RMA latency - exponentially better for small messages, then becomes gradually even for large messages in the case of put and get. Current performance detriments versus [IBM's vendor-supplied MPICH]: 1.) No optimized collectives -- all collectives are pt2pt algorithms in MPICH CH4. There is a plan to develop optimized collectives via OFI triggered operations but that work wouldn't begin until the April-May timeframe at the earliest. There is also a plan to make optimized pt2pt collectives available sooner. 2.) Only 1 rget injection fifo utilized per rank to pt2pt communication --- pami can utilize up all 11 to maximize internode bandwidth, you would mainly see this have an impact if you are running < 8 ranks per node and passing large messages. ==rob _______________________________________________ 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] Installation on Blue Gene/Q
by Latham, Robert J. 19 Apr '17

19 Apr '17

On Wed, 2017-04-19 at 13:58 +0200, pramod kumbhar wrote: > Hi Rob, > > Is this already installed/avaialble on MIRA? I would like to try this > to check some mpi i/o hints. Yes, there are several versions available: manual progress optimized: /projects/aurora_app/mpich3-ch4-ofi/install/gnu/bin auto progress optimized: /projects/aurora_app/mpich3-ch4-ofi/install-auto/gnu/bin manual progress debug: /projects/aurora_app/mpich3-ch4-ofi/install/gnu.debug/bin auto progress debug: /projects/aurora_app/mpich3-ch4-ofi/install-auto/gnu.debug/bin There are some performance considerations (both positive and negative) to consider: Current performance improvements versus [IBM's vendor-supplied MPICH]: 1.) Pt2pt latency - better than 2x speedup for small messages, large ones with few ranks-per-node less so due to detriment #2 listed below. 2.) RMA latency - exponentially better for small messages, then becomes gradually even for large messages in the case of put and get. Current performance detriments versus [IBM's vendor-supplied MPICH]: 1.) No optimized collectives -- all collectives are pt2pt algorithms in MPICH CH4. There is a plan to develop optimized collectives via OFI triggered operations but that work wouldn't begin until the April-May timeframe at the earliest. There is also a plan to make optimized pt2pt collectives available sooner. 2.) Only 1 rget injection fifo utilized per rank to pt2pt communication --- pami can utilize up all 11 to maximize internode bandwidth, you would mainly see this have an impact if you are running < 8 ranks per node and passing large messages. ==rob _______________________________________________ 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] Installation on Blue Gene/Q
by pramod kumbhar 19 Apr '17

19 Apr '17

Hi Rob, Is this already installed/avaialble on MIRA? I would like to try this to check some mpi i/o hints. Regards, Pramod Paul Coffmann put together a little build-it-all environment: > > https://github.com/pkcoff/OFI-BGQ-BuildEnv > > You might be the first on-Argonne Blue Gene to try this out: I'm sure > Paul would like to hear your experience. > > ==rob > > > > > Cheers, > > Marc-Andre > > > > On 23.03.2017 02:36, Balaji, Pavan wrote: > > > Marc-Andre, > > > > > > We dropped support for the BG/Q pamid device in mpich- > > > 3.2. However, in the mpich-3.3 series, we have brought back > > > support for BG/Q through the CH4:OFI stack. It's experimental, but > > > the performance so far is significantly better than the old pamid > > > device. Can you try that instead? > > > > > > -- Pavan > > > > > > > On Mar 22, 2017, at 2:45 PM, Marc-André Hermanns <m.a.hermanns@fz > > > > -juelich.de> wrote: > > > > > > > > Dear MPICH team, > > > > > > > > we are trying to install the latest MPICH 3.2 on our Blue Gene/Q > > > > system, but fail with both XL and clang. > > > > > > > > A colleague forwarded the make error log from his try using XL: > > > > > > > > make[2]: Entering directory > > > > `/homeb/zam/scprod/mstephan/mpich3/mpich-3.2' > > > > CC src/mpi/attr/lib_libmpi_la-attr_delete.lo > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidi_thread.h", > > > > line 64.9: 1506-236 (W) Macro name MPIU_THREAD_CS_ENTER has been > > > > redefined. > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidi_thread.h", > > > > line 64.9: 1506-358 (I) "MPIU_THREAD_CS_ENTER" is defined on line > > > > 80 > > > > of ./src/util/thread/mpiu_thread_multiple.h. > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidi_thread.h", > > > > line 65.9: 1506-236 (W) Macro name MPIU_THREAD_CS_EXIT has been > > > > redefined. > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidi_thread.h", > > > > line 65.9: 1506-358 (I) "MPIU_THREAD_CS_EXIT" is defined on line > > > > 81 of > > > > ./src/util/thread/mpiu_thread_multiple.h. > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidi_thread.h", > > > > line 66.9: 1506-236 (W) Macro name MPIU_THREAD_CS_YIELD has been > > > > redefined. > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidi_thread.h", > > > > line 66.9: 1506-358 (I) "MPIU_THREAD_CS_YIELD" is defined on line > > > > 82 > > > > of ./src/util/thread/mpiu_thread_multiple.h. > > > > "./src/include/mpiimpl.h", line 1184.5: 1506-046 (S) Syntax > > > > error. > > > > "./src/include/mpiimpl.h", line 1481.5: 1506-046 (S) Syntax > > > > error. > > > > "./src/include/mpiimpl.h", line 1636.5: 1506-046 (S) Syntax > > > > error. > > > > "./src/include/mpiimpl.h", line 2785.5: 1506-343 (S) > > > > Redeclaration of > > > > MPID_Send differs from previous declaration on line 2760 of > > > > "./src/include/mpiimpl.h". > > > > "./src/include/mpiimpl.h", line 2785.5: 1506-377 (I) The type > > > > "int" of > > > > parameter 2 differs from the previous type "long". > > > > "./src/include/mpiimpl.h", line 2884.5: 1506-343 (S) > > > > Redeclaration of > > > > MPID_Isend differs from previous declaration on line 2865 of > > > > "./src/include/mpiimpl.h". > > > > "./src/include/mpiimpl.h", line 2884.5: 1506-377 (I) The type > > > > "int" of > > > > parameter 2 differs from the previous type "long". > > > > "./src/include/mpitimpl.h", line 245.5: 1506-046 (S) Syntax > > > > error. > > > > "./src/include/mpitimpl.h", line 900.40: 1506-022 (S) "total" is > > > > not a > > > > member of "struct {...}". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/../src/mpid_request.h", > > > > line 156.21: 1506-022 (S) "cc" is not a member of "struct > > > > MPID_Request". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/../src/mpid_request.h", > > > > line 157.8: 1506-022 (S) "cc_ptr" is not a member of "struct > > > > MPID_Request". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/../src/mpid_request.h", > > > > line 157.23: 1506-022 (S) "cc" is not a member of "struct > > > > MPID_Request". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/../src/mpid_request.h", > > > > line 283.62: 1506-099 (S) Unexpected argument. > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/../src/mpid_request.h", > > > > line 326.23: 1506-022 (S) "cc_ptr" is not a member of "struct > > > > MPID_Request". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/../src/mpid_request.h", > > > > line 341.23: 1506-022 (S) "cc_ptr" is not a member of "struct > > > > MPID_Request". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidpost.h", > > > > line 56.44: 1506-022 (S) "vcr" is not a member of "struct > > > > MPID_Comm". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidpost.h", > > > > line 83.43: 1506-022 (S) "vcrt" is not a member of "struct > > > > MPID_Comm". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidpost.h", > > > > line 84.37: 1506-022 (S) "vcrt" is not a member of "struct > > > > MPID_Comm". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidpost.h", > > > > line 84.57: 1506-022 (S) "vcr" is not a member of "struct > > > > MPID_Comm". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidpost.h", > > > > line 91.42: 1506-022 (S) "vcr" is not a member of "struct > > > > MPID_Comm". > > > > "/homeb/zam/scprod/mstephan/mpich3/mpich- > > > > 3.2/src/mpid/pamid/include/mpidpost.h", > > > > line 92.41: 1506-022 (S) "vcr" is not a member of "struct > > > > MPID_Comm". > > > > "src/mpi/attr/attr_delete.c", line 65.26: 1506-045 (S) Undeclared > > > > identifier GLOBAL. > > > > make[2]: *** [src/mpi/attr/lib_libmpi_la-attr_delete.lo] Error 1 > > > > make[2]: Leaving directory > > > > `/homeb/zam/scprod/mstephan/mpich3/mpich-3.2' > > > > make[1]: *** [all-recursive] Error 1 > > > > make[1]: Leaving directory > > > > `/homeb/zam/scprod/mstephan/mpich3/mpich-3.2' > > > > make: *** [all] Error 2 > > > > > > > > Is there something obvious that we missed? > > > > > > > > Cheers, > > > > Marc-Andre > > > > > > > > -- > > > > Marc-Andre Hermanns > > > > Jülich Aachen Research Alliance, > > > > High Performance Computing (JARA-HPC) > > > > Jülich Supercomputing Centre (JSC) > > > > > > > > Wilhelm-Johnen-Str. > > > > 52425 Jülich > > > > Germany > > > > > > > > Phone: +49 2461 61 2509 | +49 241 80 24381 > > > > Fax: +49 2461 80 6 99753 > > > > www.jara.org/jara-hpc > > > > email: m.a.hermanns(a)fz-juelich.de > > > > > > > > _______________________________________________ > > > > 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 > _______________________________________________ > 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] mpicc -V broken
by Min Si 18 Apr '17

18 Apr '17

Your `mpicc -show` output shows there is no bug in mpicc script. I tried to configure mpiblast with MPICH v3.2 release. I see a slightly different error reported if searching `mpicc -V` in config.log, but the configure is completed without any error. I think the configure just tries to get some compiler information through common options such as `--version`, `-v`, or `-V`. But it does not break the configure if any of those options is unsupported. So you can just ignore this error message. Please let us know if you find other problem break the compiling. Btw, here is the error message on my side. I think we see different errors for `-V` option just because of a different GCC version. gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) configure:2855: $? = 0 configure:2862: /home/minsi/git/mpich.git.v3.2/build-gnu-tcp/install/bin/mpicc -V >&5 gcc: error: unrecognized command line option '-V' Min On 4/17/17 4:50 PM, Chandler wrote: > Min Si wrote on 04/15/2017 11:02 AM: >> Can you try `mpicc -show` ? > > $ mpicc -show > gcc -I/opt/mpich-install/include -L/opt/mpich-install/lib -Wl,-rpath > -Wl,/opt/mpich-install/lib -Wl,--enable-new-dtags -lmpi > >> Is "mpicc -V" checked by mpiblast configure? > > Yes. I attached config.log > > > On 4/15/17 11:01 AM, Jeff Hammond wrote: >>> Try "mpicc -v". I don't remember if GCC version flag is case >>> insensitive. > > Yes mpicc -v does work as expected > > > > _______________________________________________ > 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] Fatal error in MPI_Finalize: Other MPI error, error stack:
by Halim Amer 18 Apr '17

18 Apr '17

Jeff, Have you encountered the same problem on a Linux platform or a non-Intel compiler? I could not reproduce the problem on my Mac with gcc-6. Halim www.mcs.anl.gov/~aamer On 4/12/17 10:04 AM, Jeff Hammond wrote: > I observe this crash during MPI_Finalize in an ARMCI-MPI unit test > (test_malloc) that was not failing until I switched to using OFI-based > MPICH on my Mac laptop. Any suggestions on how to debug? > > Jeff > > Abort(806972175) on node 0 (rank 0 in comm 0): Fatal error in > MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(317)..........: MPI_Finalize failed > MPI_Finalize(239)..........: > MPID_Finalize(318).........: > MPIDI_NM_mpi_init_hook(948): OFI av close failed > (ofi_init.h:948:MPIDI_NM_mpi_init_hook:Resource busy) > Abort(806972175) on node 1 (rank 1 in comm 0): Fatal error in > MPI_Finalize: Other MPI error, error stack: > MPI_Finalize(317)..........: MPI_Finalize failed > MPI_Finalize(239)..........: > MPID_Finalize(318).........: > MPIDI_NM_mpi_init_hook(948): OFI av close failed > (ofi_init.h:948:MPIDI_NM_mpi_init_hook:Resource busy) > > $ mpicc -show > icc -g -Wl,-commons,use_dylibs -I/opt/mpich/dev/intel/default/include > -L/opt/mpich/dev/intel/default/lib -lmpi -lpmpi > > $ mpichversion > MPICH Version: 3.3a2 > MPICH Release date: unreleased development copy > MPICH Device: ch4:ofi > MPICH configure: CC=icc CXX=icpc FC=ifort F77=ifort --enable-cxx > --enable-fortran --enable-threads=runtime --enable-g=dbg --with-pm=hydra > --prefix=/opt/mpich/dev/intel/default --enable-wrapper-rpath > --enable-two-level-namespace --disable-static --enable-shared > --with-device=ch4:ofi --with-libfabric=/usr/local/Cellar/libfabric/1.4.1 > MPICH CC: icc -g -O2 > MPICH CXX: icpc -g > MPICH F77: ifort -g -O2 > MPICH FC: ifort -g -O2 > MPICH Custom Information: > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > http://jeffhammond.github.io/ > > > _______________________________________________ > 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] mpicc -V broken
by Chandler 17 Apr '17

17 Apr '17

Min Si wrote on 04/15/2017 11:02 AM: > Can you try `mpicc -show` ? $ mpicc -show gcc -I/opt/mpich-install/include -L/opt/mpich-install/lib -Wl,-rpath -Wl,/opt/mpich-install/lib -Wl,--enable-new-dtags -lmpi > Is "mpicc -V" checked by mpiblast configure? Yes. I attached config.log On 4/15/17 11:01 AM, Jeff Hammond wrote: >> Try "mpicc -v". I don't remember if GCC version flag is case insensitive. Yes mpicc -v does work as expected _______________________________________________ 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] MPICH with IPv6
by Min Si 15 Apr '17

15 Apr '17

Hi, I found a similar question about IPv6 in MPICH2. It seems IPv6 is supported in MPICH. http://lists.mpich.org/pipermail/discuss/2013-October/001613.html Can you please send us more information about your problem ? - Your MPICH version - Your MPICH config.log (you can find it in the build directory) - What is your problem Thanks, Min On 4/3/17 7:09 PM, Santiago Lambrisca wrote: > Hello, > > I am trying to use MPICH to connect several hosts through IPv6, and > got some problems. > I am not sure if it's supported, and could not find any documentation > talking about that. > I would like to know if its supported, and if any configuration is > required to get it working. > > Thanks in advance, > > Santiago. > > > _______________________________________________ > 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] Process Group Collision for multiple clients from different host machines having same pid with MPI_Comm_accept
by Min Si 15 Apr '17

15 Apr '17

Hi Hirak, Before look into PMI, it would be good to first make sure if this is a problem in your server-client code, or in the dynamic process part of MPICH code. Could you please reproduce this issue with a simple program and give it to us ? One thing I noticed is that the server program is multithreaded. Are you using multiple threads to accept client connection ? Anyway, a reproducer program will be great. Please also try to use the latest MPICH release and see if it happens. In summary, it would be great if you can send us the following files. - A reproducer program - MPICH's config.log (you can find it in the directory where you build MPICH) Thanks, Min On 4/14/17 1:15 AM, Roy, Hirak wrote: > > > Dear MPICH team, > > We use MPICH for a server-client application. We use MPICH-3.0.4 with > sock channel. > In this application there is one server and 100 clients. > Each client is launched independently in different host-machines using > individual-wrapper scripts. (we explicitly use : mpiexec -n 1 ) > > The server is multithreaded and it uses MPI_Comm_accept (on > MPI_COMM_SELF) and clients use MPI_Comm_connect to connect. > We have observed the following issue after all the clients connect to > server : > if we send message to a client (lets say 'm'), it reaches > unexpectedly to some other client (lets say 'n'). { server sends the > message using the communicator returned by accept call }. This happens > randomly in one out of 5-6 runs. > > On further looking into MPICH code, we found that > 1) There is a collsion of pg (process-group) of two processes (m and > n) after mpi-comm-accept > 2) As a result of (1), comm->vc are same (for m and n, although comm > are different). It seems that the unique string (something like > kva_<int>_int) is not unique for such two processes. 'm' and 'n' > processes are running in different host-machine and they have the same > pid. The kva string looked like kva_pid_rank. > > > We have the following questions : > 1) Have we built MPICH with some kind of incorrect > configuration (hydra configuration at the end of the email) ? > 2) Are we using incorrect process-manager or configuration and that is > why there is a possible collision of process-groups? > 3) What is the purpose of process group sharing/uniquifying? If there > is no real reason for this, could it be disabled or will something > else rely on the id string being unique? > 4) If there are no other work-around, what could be done to make the > id string unique? Add the host-name? Will everything else be ok with this? > > > It would be good if you can let us know if there is any workaround for > this issue or not. > > > Thanks, > Hirak Roy > > HYDRA build details: > CXX: no -O3 -fPIC > F77: no > F90: no > Configure options: '--disable-option-checking' > '--prefix=/home/hroy/local/mpich-3.0.4/linux_x86_64' '--disable-f77' > '--disable-fc' '--disable-f90modules' '--disable-cxx' > '--enable-fast=nochkmsg' '--enable-fast=notiming' > '--enable-fast=ndebug' '--enable-fast=O3' '--with-device=ch3:sock' > 'CFLAGS=-O3 -fPIC -O3' 'CXXFLAGS=-O3 -fPIC ' > 'CC=/u/prod/gnu/gcc/20121129/gcc-4.5.0-linux_x86_64/bin/gcc' 'LDFLAGS= > ' '--cache-file=/dev/null' '--srcdir=.' 'LIBS=-lrt -lpthread ' > 'CPPFLAGS= -I/home/hroy/tools/mpich/mpich-3.0.4/src/mpl/include > -I/home/hroy/tools/mpich/mpich-3.0.4/src/mpl/include > -I/home/hroy/tools/mpich/mpich-3.0.4/src/openpa/src > -I/home/hroy/tools/mpich/mpich-3.0.4/src/openpa/src > -I/home/hroy/tools/mpich/mpich-3.0.4/src/mpi/romio/include' > Process Manager: pmi > Launchers available: ssh rsh fork slurm ll lsf > sge manual persist > Topology libraries available: hwloc > Resource management kernels available: user slurm ll lsf sge pbs > cobalt > Checkpointing libraries available: > Demux engines available: poll select > > > > _______________________________________________ > 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] mpicc -V broken
by Min Si 15 Apr '17

15 Apr '17

Can you try `mpicc -show` ? It will show all compiling options added by MPICH. Is "mpicc -V" checked by mpiblast configure ? If it is, can you please attach the failing config.log ? Thanks, Min On 4/15/17 11:01 AM, Jeff Hammond wrote: > Try "mpicc -v". I don't remember if GCC version flag is case insensitive. > > In any case, you can edit "which mpicc" to see if there is an issue > there. It's a plain text file. > > Jeff > > On Fri, Apr 14, 2017 at 5:14 PM Sobel-Sorenson, Chandler - (scar) > <scar(a)email.arizona.edu <mailto:[email protected]>> wrote: > > I have just installed mpich 3.2 on our CentOS 6.8 machine with gcc > 4.4.7. It worked fine with maker but now am having a strange > issue when trying to install mpiblast. I noticed a problem when > "mpicc -V" is run, for example: > > $ mpicc -V > gcc: error trying to exec > 'x86_64-redhat-linux-gcc--I/opt/mpich-install/include': execvp: No > such file or directory > > It seems that a space is missing, because when I run > "x86_64-redhat-linux-gcc --I/opt/mpich-install/include" it says > "x86_64-redhat-linux-gcc: no input files" > > I'm not sure how this happened, maybe it is a bug? I did a > standard installation with "./configure > --prefix=/opt/mpich-install; make; make install" > > If you know how I could fix this or if you need more info about > our system/installation then please let me know! > > Thanks > Chandler / Systems Administrator > Arizona Genomics Institute > www.genome.arizona.edu <http://www.genome.arizona.edu> > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > http://jeffhammond.github.io/ > > > _______________________________________________ > 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] mpicc -V broken
by Jeff Hammond 15 Apr '17

15 Apr '17

Try "mpicc -v". I don't remember if GCC version flag is case insensitive. In any case, you can edit "which mpicc" to see if there is an issue there. It's a plain text file. Jeff On Fri, Apr 14, 2017 at 5:14 PM Sobel-Sorenson, Chandler - (scar) < scar(a)email.arizona.edu> wrote: > I have just installed mpich 3.2 on our CentOS 6.8 machine with gcc 4.4.7. > It worked fine with maker but now am having a strange issue when trying to > install mpiblast. I noticed a problem when "mpicc -V" is run, for example: > > $ mpicc -V > gcc: error trying to exec > 'x86_64-redhat-linux-gcc--I/opt/mpich-install/include': execvp: No such > file or directory > > It seems that a space is missing, because when I run > "x86_64-redhat-linux-gcc --I/opt/mpich-install/include" it says > "x86_64-redhat-linux-gcc: no input files" > > I'm not sure how this happened, maybe it is a bug? I did a standard > installation with "./configure --prefix=/opt/mpich-install; make; make > install" > > If you know how I could fix this or if you need more info about our > system/installation then please let me know! > > Thanks > Chandler / Systems Administrator > Arizona Genomics Institute > www.genome.arizona.edu > _______________________________________________ > 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