discuss

Download

[email protected]

January 2013

29 participants
132 discussions

Re: [mpich-discuss] Error in c.txt nemesis does not exist
by behzad moradi 01 Jan '13

01 Jan '13

can't exec '/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2' (No such file or directory) What is this error? On Dec 24, 2012, at 5:33 AM, Pavan Balaji wrote: > > I'm cc'ing our Windows expert, Jayesh. He might know what's going on. > > -- Pavan > > On 12/05/2012 03:27 PM US Central Time, Ayesha Ghani wrote: >> Hi Dave >> >> >> Thanks for your help! I have tried to install a few versions of MPICH2 >> on cygwin now. >> >> For version 2-1.4, the c.txt file seems fine (no errors) but the m.txt >> file goes on for a while 'Entering directory' and 'Leaving directory' >> and then at the end outputs an error. >> >> make[1]: *** No rule to make target >> '/home/agha023/libraries/mpich2-1.4/src/mpl/Makefile.am' needed by >> '/home/agha023/libraries/mpich2-1.4/src/mpl/Makefile.in'. Stop >> make: *** [all-redirect] Error 1 >> >> >> From searching up forums this error occurs because make couldnt find >> instructions in the Makefile.in to build the target. However Makefile.am >> and Makefile.in both exist in the directory above. >> >> Again however I can't find a solution to this problem and would greatly >> appreciate any help. >> >> Should I email the m.txt and c.txt files? >> >> >> Kind Regards >> Ayesha Ghani >> >> >> >> >> >> >> >> >> On 6 December 2012 08:03, Dave Goodell <goodell(a)mcs.anl.gov >> <mailto:[email protected]>> wrote: >> >> Try using mpich2-1.4 instead. It would not be surprising if there >> was a problem with 1.5 on cygwin. >> >> -Dave >> >> On Dec 4, 2012, at 8:48 PM PST, Ayesha Ghani wrote: >> >>> Hello >>> >>> >>> I was working through the installation instructions for mpich2 >> very carefully this time and my .c file has an error at the end: >>> 'immediate ERROR: nemesis does not exist' >>> >>> I would appreciate any assistance. >>> >>> >>> Kind Regards >>> Ayesha >>> <c.txt>_______________________________________________ >>> 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 <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 >> > > -- > Pavan Balaji > http://www.mcs.anl.gov/~balaji > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

building mpich2 with open64 compilers is difficult
by Michael Seman 31 Dec '12

31 Dec '12

I built mpich2 before with gcc and Intel compilers. I tried to compile with open64, so first tried mpich2-1.2.1p1 which I built with other compilers. The make proceeds, I see lot of CC commands, then at the first F90, it falls over. So I added the verbosity option V=1 to the make and tried again. When it got up to the offending "F90 mpi.f90" stage, I now see this at the tail of the make log: date > .libstamp1 make[4]: Leaving directory `/home/michael/apps/thirdparty/mpich2-1.2.1p1/src/binding/f90' make[4]: Entering directory `/home/michael/apps/thirdparty/mpich2-1.2.1p1/src/binding/f90' false -O2 -I. -c mpi.f90 -o _smpi.o mv -f _smpi.o mpi.lo make[4]: *** [mpi.lo] Error 1 make[4]: Leaving directory `/home/michael/apps/thirdparty/mpich2-1.2.1p1/src/binding/f90' make[3]: *** [all-redirect] Error 1 make[3]: Leaving directory `/home/michael/apps/thirdparty/mpich2-1.2.1p1/src/binding/f90' make[2]: *** [all-redirect] Error 1 make[2]: Leaving directory `/home/michael/apps/thirdparty/mpich2-1.2.1p1/src/binding' make[1]: *** [all-redirect] Error 2 make[1]: Leaving directory `/home/michael/apps/thirdparty/mpich2-1.2.1p1/src' make: *** [all-redirect] Error 2 So "F90" has become "false" somewhere along the track. Configure variables were for 1.2.1p1: BUILD_DIR=/usr/local F90=openf90 F77=openf90 CC=opencc CXX=openCC CFLAGS="-fPIC -O" FFLAGS="-fPIC -fno-second-underscore -O" F90FLAGS="-fPIC -fno-second-underscore -O" FLAGS="--prefix=${BUILD_DIR} --enable-threads --enable-sharedlibs=gcc \ --enable-f77 --enable-f90 --enable-cxx" Next, I tried version 1.4 of mpich2, which requires changing a few things, such as F90 to FC and --enable-f90 to --enable-fc and adding --enabled-shared to flags. I used these configure variables with versions 1.3 to 1.5: BUILD_DIR=/usr/local F77=openf90 FC=openf90 CC=opencc CXX=openCC CFLAGS="-fPIC -O" FFLAGS="-fPIC -fno-second-underscore -O" FCFLAGS="-fPIC -fno-second-underscore -O" F77FLAGS="-fPIC -fno-second-underscore -O" FLAGS="--prefix=${BUILD_DIR} --enable-threads --enable-sharedlibs=gcc \ --enable-fc --enable-shared --enable-f77 --enable-cxx" Again this flops when make gets up to mpi.f90. I still see "false" instead of the FC compiler command. Only version 1.5 of mpich2 can be built okay with open64 compilers. I used version 4.2.4 of open64 under RHEL 5.8 64-bit. I also tried open64 version 4.2.1 Has anybody found other combinations to build mpich2 using open64?

1 0

Jump to page: