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

Re: [mpich-discuss] MPICH install failure
by Wesley Bland 09 Sep '13

09 Sep '13

It looks like you had some sort of issue in your configure step so the Makefiles were never generated. Can you send the config.log? It has much more useful information than c.txt. Although, on first glance, it appears that you don't have any C++ compiler installed. It's not necessary to do so, but if you don't want it, you need to specify that in your configure by adding `--disable-cxx` to your ./configure line. Thanks, Wesley On Sep 9, 2013, at 7:35 AM, Amogh Katti <A.P.Katti(a)pgr.reading.ac.uk> wrote: > Hello, > > I am a beginner to MPI programming. I tried to install MPICH and the build step failed saying, "No targets specified and no make file found". I have attached the c.txt and m.txt; Please help. > > Many thanks, > Amogh. > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH install failure
by Amogh Katti 09 Sep '13

09 Sep '13

Hello, I am a beginner to MPI programming. I tried to install MPICH and the build step failed saying, "No targets specified and no make file found". I have attached the c.txt and m.txt; Please help. Many thanks, Amogh.

1 0

MPICH install failure
by Amogh Katti 09 Sep '13

09 Sep '13

Hello, I am a beginner to MPI programming. I tried to install MPICH and the build step failed saying, "No targets specified and no make file found". I have attached the c.txt and m.txt; Please help. Many thanks, Amogh.

1 0

Re: [mpich-discuss] libintlc.so.5 not found while configuring
by Reuti 06 Sep '13

06 Sep '13

Am 06.09.2013 um 04:45 schrieb Seungbum Koo: > I think I got it. Doing everything in root privilege solved that library recognition problem as well as 'mpd' and other bugging issues. I don't know why those happened while sticking to 'sudo', but I can now compile and run with MPICH 3.0.4 and Intel compiler 14.0.0. `sudo` can be configured to reset all, or some environment variables while keeping others, change the home directory... Maybe something was reset. -- Reuti > Sorry for bothering. > > > On Thu, Sep 5, 2013 at 7:42 PM, Seungbum Koo <doougsini(a)gmail.com> wrote: > It should work. 'icc' command works regardless of 'pwd'. So as 'ifort'. I just programmed Hello World! in both C and FORTRAN and they all compiled well and ran successfully. Even for the intel provided sample c source code(one that is in /intel/sample/). I could compile it and successfully run it. > > Maybe it's version problem. I'll downgrade intel compiler and see if it works in that case. > > > On Thu, Sep 5, 2013 at 7:09 PM, Antonio J. Peña <apenya(a)mcs.anl.gov> wrote: > > Seungbum, > > I've checked your configure flags in our testbed. I find no problems even without the LDFLAGS parameter. Have you tried to compile any other code with your icc setup? I bet there's something wrong with your icc setup. Have you executed the iccvars.sh script? (BTW, we use icc 13.1.3). > > Antonio > > > On Thursday, September 05, 2013 06:34:08 PM Seungbum Koo wrote: > Thank you for your advice. But nothing has changed even if I add that line at the stage of configure. > > So this is what I wrote in the command line. > > ======================================================================== > sudo /opt/mpich/mpich-3.0.4-source/configure --prefix=/opt/mpich/ CC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icc CXX=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icpc F77=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort FC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort LDFLAGS="-L/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64" --enable-fast=all,O3 --enable-g=dbg,mem,log --enable-shared --with-pm=hydra 2>&1 | sudo tee log_configure.txt > ================================================================ > > What 'configure' says: > ====================================================== > ld: warning: libintlc.so.5, needed by /opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/libifport.so.5, not found (try using -rpath or -rpath-link) > ====================================================== > > What 'make' says: > > ================================================================ > ld: warning: libimf.so, needed by /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using -rpath or -rpath-link) > ld: warning: libsvml.so, needed by /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using -rpath or -rpath-link) > ld: warning: libirng.so, needed by /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using -rpath or -rpath-link) > ld: warning: libintlc.so.5, needed by /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using -rpath or -rpath-link) > ================================================================ > > Not a single line difference as before. > > Does it make sense? "libifport.so.5" needs "libintlc.so.5" but they are in the same directory. And those 'not found' files at the 'make' stage as well. They are all in '/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/'. > > Any idea? > > > Seungbum > > > _______________________________________________ > 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] libintlc.so.5 not found while configuring
by Seungbum Koo 05 Sep '13

05 Sep '13

I think I got it. Doing everything in root privilege solved that library recognition problem as well as 'mpd' and other bugging issues. I don't know why those happened while sticking to 'sudo', but I can now compile and run with MPICH 3.0.4 and Intel compiler 14.0.0. Sorry for bothering. On Thu, Sep 5, 2013 at 7:42 PM, Seungbum Koo <doougsini(a)gmail.com> wrote: > It should work. 'icc' command works regardless of 'pwd'. So as 'ifort'. I > just programmed Hello World! in both C and FORTRAN and they all compiled > well and ran successfully. Even for the intel provided sample c source > code(one that is in /intel/sample/). I could compile it and successfully > run it. > > Maybe it's version problem. I'll downgrade intel compiler and see if it > works in that case. > > > On Thu, Sep 5, 2013 at 7:09 PM, Antonio J. Peña <apenya(a)mcs.anl.gov>wrote: > >> ** >> >> >> >> Seungbum, >> >> >> >> I've checked your configure flags in our testbed. I find no problems even >> without the LDFLAGS parameter. Have you tried to compile any other code >> with your icc setup? I bet there's something wrong with your icc setup. >> Have you executed the iccvars.sh script? (BTW, we use icc 13.1.3). >> >> >> >> Antonio >> >> >> >> >> >> On Thursday, September 05, 2013 06:34:08 PM Seungbum Koo wrote: >> >> Thank you for your advice. But nothing has changed even if I add that >> line at the stage of configure. >> >> So this is what I wrote in the command line. >> >> >> ======================================================================== >> sudo /opt/mpich/mpich-3.0.4-source/configure --prefix=/opt/mpich/ >> CC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icc >> CXX=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icpc >> F77=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort >> FC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort >> LDFLAGS="-L/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64" >> --enable-fast=all,O3 --enable-g=dbg,mem,log --enable-shared --with-pm=hydra >> 2>&1 | sudo tee log_configure.txt >> ================================================================ >> >> What 'configure' says: >> ====================================================== >> >> ld: warning: libintlc.so.5, needed by >> /opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/libifport.so.5, >> not found (try using -rpath or -rpath-link) >> ====================================================== >> >> What 'make' says: >> >> >> ================================================================ >> ld: warning: libimf.so, needed by >> /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using >> -rpath or -rpath-link) >> ld: warning: libsvml.so, needed by >> /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using >> -rpath or -rpath-link) >> ld: warning: libirng.so, needed by >> /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using >> -rpath or -rpath-link) >> ld: warning: libintlc.so.5, needed by >> /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using >> -rpath or -rpath-link) >> ================================================================ >> >> Not a single line difference as before. >> >> >> Does it make sense? "libifport.so.5" needs "libintlc.so.5" but they are >> in the same directory. And those 'not found' files at the 'make' stage as >> well. They are all in >> '/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/'. >> >> Any idea? >> >> >> >> Seungbum >> >> >> >> _______________________________________________ >> 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] Do I need to run "mpd" every time before I execute "mpiexec"?
by Pavan Balaji 05 Sep '13

05 Sep '13

That's not possible, unless there are other options you are passing to configure that you didn't mention here. With mpich-3.0.4, --with-pm=hydra is default. So whether you pass it or not, there's no difference in the build. -- Pavan On Sep 5, 2013, at 8:14 PM, Seungbum Koo wrote: > Yes the build failed without "--with-pm=hydra". I reconfigured "--with-pm=hydra" and then it worked. > > I'm struggling with other issue though... > > > On Thu, Sep 5, 2013 at 8:04 PM, Pavan Balaji <balaji(a)mcs.anl.gov> wrote: > > Is the build failing without --with-pm=hydra? > > -- Pavan > > On Sep 5, 2013, at 2:26 PM, Seungbum Koo wrote: > > > Sorry. The log file at the stage of the problem is overwritten when I was reconfiguring MPICH again. > > > > I don't know if it will help, but I attached 'config.log' I just ran without "--with-pm=hydra" option. > > > > Seungbum > > > > > > On Thu, Sep 5, 2013 at 9:07 AM, Ken Raffenetti <raffenet(a)mcs.anl.gov> wrote: > > You should not have to specify hydra with the 3.0.4 release. It is the default. Can you send your config.log so we know what went wrong? > > > > ----- Original Message ----- > > > From: "Seungbum Koo" <doougsini(a)gmail.com> > > > To: "Jeff Hammond" <jeff.science(a)gmail.com>, nrosner(a)gmail.com > > > Cc: "MPICH" <discuss(a)mpich.org> > > > Sent: Thursday, September 5, 2013 6:59:12 AM > > > Subject: Re: [mpich-discuss] Do I need to run "mpd" every time before I execute "mpiexec"? > > > > > > > > > > > > > > > > > > Wow. Thank you for the fast replies. You guys hardly sleep. > > > > > > PROBLEM SOLVED. It works now. > > > > > > Nicolás/ No. that can't be. It is my personal computer and I haven't > > > installed MPICH so far. > > > Jeff/ I saw that FAQ but didn't try --with-pm=hydra. > > > > > > > > > > > > I first didn't configure MPICH with any process manager since hydra > > > is set to default according to the installation guide. I > > > reconfigured "--with-pm=hydra" and reinstalled. Now it is working. > > > > > > > > > Once again, thank you for your interest and help. > > > > > > Seungbum > > > > > > > > > > > > > > > On Wed, Sep 4, 2013 at 11:14 PM, Jeff Hammond < > > > jeff.science(a)gmail.com > wrote: > > > > > > > > > > > > http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_I_don.2… > > > > > > > > > > > > > > > > > > > > > On Wed, Sep 4, 2013 at 11:02 PM, Nicolas Rosner < nrosner(a)gmail.com > > > > wrote: > > > > > > > > > > > > > > > Hi Seungbum, > > > > > > > > > > do I need to run "mpd" every time before I run "mpiexec"? > > > > > > No. You shouldn't need to run mpd at all. > > > > > > From the FAQ: "The mpd process manager has many problems, as well as > > > an annoying mpdboot step that is fragile and difficult to use > > > correctly. The mpd process manager is deprecated at this point ..." > > > > > > Perhaps when you typed "mpiexec", you were not really running the > > > mpiexec binary that you had just built, but rather some other (really > > > old) version that was already lying around on your system? > > > > > > I'd suggest: > > > running "which mpiexec" and "mpiexec --version" > > > checking your $PATH > > > specifying an absolute pathname to the new mpiexec binary instead > > > of just "mpiexec" > > > > > > Hope this helps, > > > Nicolás > > > _______________________________________________ > > > 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 > > > > > > _______________________________________________ > > > 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 > > > > <config.log>_______________________________________________ > > 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 > > _______________________________________________ > 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

1 0

Re: [mpich-discuss] Do I need to run "mpd" every time before I execute "mpiexec"?
by Seungbum Koo 05 Sep '13

05 Sep '13

Yes the build failed without "--with-pm=hydra". I reconfigured "--with-pm=hydra" and then it worked. I'm struggling with other issue though... On Thu, Sep 5, 2013 at 8:04 PM, Pavan Balaji <balaji(a)mcs.anl.gov> wrote: > > Is the build failing without --with-pm=hydra? > > -- Pavan > > On Sep 5, 2013, at 2:26 PM, Seungbum Koo wrote: > > > Sorry. The log file at the stage of the problem is overwritten when I > was reconfiguring MPICH again. > > > > I don't know if it will help, but I attached 'config.log' I just ran > without "--with-pm=hydra" option. > > > > Seungbum > > > > > > On Thu, Sep 5, 2013 at 9:07 AM, Ken Raffenetti <raffenet(a)mcs.anl.gov> > wrote: > > You should not have to specify hydra with the 3.0.4 release. It is the > default. Can you send your config.log so we know what went wrong? > > > > ----- Original Message ----- > > > From: "Seungbum Koo" <doougsini(a)gmail.com> > > > To: "Jeff Hammond" <jeff.science(a)gmail.com>, nrosner(a)gmail.com > > > Cc: "MPICH" <discuss(a)mpich.org> > > > Sent: Thursday, September 5, 2013 6:59:12 AM > > > Subject: Re: [mpich-discuss] Do I need to run "mpd" every time before > I execute "mpiexec"? > > > > > > > > > > > > > > > > > > Wow. Thank you for the fast replies. You guys hardly sleep. > > > > > > PROBLEM SOLVED. It works now. > > > > > > Nicolás/ No. that can't be. It is my personal computer and I haven't > > > installed MPICH so far. > > > Jeff/ I saw that FAQ but didn't try --with-pm=hydra. > > > > > > > > > > > > I first didn't configure MPICH with any process manager since hydra > > > is set to default according to the installation guide. I > > > reconfigured "--with-pm=hydra" and reinstalled. Now it is working. > > > > > > > > > Once again, thank you for your interest and help. > > > > > > Seungbum > > > > > > > > > > > > > > > On Wed, Sep 4, 2013 at 11:14 PM, Jeff Hammond < > > > jeff.science(a)gmail.com > wrote: > > > > > > > > > > > > > http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_I_don.2… > > > > > > > > > > > > > > > > > > > > > On Wed, Sep 4, 2013 at 11:02 PM, Nicolas Rosner < nrosner(a)gmail.com > > > > wrote: > > > > > > > > > > > > > > > Hi Seungbum, > > > > > > > > > > do I need to run "mpd" every time before I run "mpiexec"? > > > > > > No. You shouldn't need to run mpd at all. > > > > > > From the FAQ: "The mpd process manager has many problems, as well as > > > an annoying mpdboot step that is fragile and difficult to use > > > correctly. The mpd process manager is deprecated at this point ..." > > > > > > Perhaps when you typed "mpiexec", you were not really running the > > > mpiexec binary that you had just built, but rather some other (really > > > old) version that was already lying around on your system? > > > > > > I'd suggest: > > > running "which mpiexec" and "mpiexec --version" > > > checking your $PATH > > > specifying an absolute pathname to the new mpiexec binary instead > > > of just "mpiexec" > > > > > > Hope this helps, > > > Nicolás > > > _______________________________________________ > > > 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 > > > > > > _______________________________________________ > > > 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 > > > > <config.log>_______________________________________________ > > 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

Re: [mpich-discuss] Do I need to run "mpd" every time before I execute "mpiexec"?
by Pavan Balaji 05 Sep '13

05 Sep '13

Is the build failing without --with-pm=hydra? -- Pavan On Sep 5, 2013, at 2:26 PM, Seungbum Koo wrote: > Sorry. The log file at the stage of the problem is overwritten when I was reconfiguring MPICH again. > > I don't know if it will help, but I attached 'config.log' I just ran without "--with-pm=hydra" option. > > Seungbum > > > On Thu, Sep 5, 2013 at 9:07 AM, Ken Raffenetti <raffenet(a)mcs.anl.gov> wrote: > You should not have to specify hydra with the 3.0.4 release. It is the default. Can you send your config.log so we know what went wrong? > > ----- Original Message ----- > > From: "Seungbum Koo" <doougsini(a)gmail.com> > > To: "Jeff Hammond" <jeff.science(a)gmail.com>, nrosner(a)gmail.com > > Cc: "MPICH" <discuss(a)mpich.org> > > Sent: Thursday, September 5, 2013 6:59:12 AM > > Subject: Re: [mpich-discuss] Do I need to run "mpd" every time before I execute "mpiexec"? > > > > > > > > > > > > Wow. Thank you for the fast replies. You guys hardly sleep. > > > > PROBLEM SOLVED. It works now. > > > > Nicolás/ No. that can't be. It is my personal computer and I haven't > > installed MPICH so far. > > Jeff/ I saw that FAQ but didn't try --with-pm=hydra. > > > > > > > > I first didn't configure MPICH with any process manager since hydra > > is set to default according to the installation guide. I > > reconfigured "--with-pm=hydra" and reinstalled. Now it is working. > > > > > > Once again, thank you for your interest and help. > > > > Seungbum > > > > > > > > > > On Wed, Sep 4, 2013 at 11:14 PM, Jeff Hammond < > > jeff.science(a)gmail.com > wrote: > > > > > > > > http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_I_don.2… > > > > > > > > > > > > > > On Wed, Sep 4, 2013 at 11:02 PM, Nicolas Rosner < nrosner(a)gmail.com > > > wrote: > > > > > > > > > > Hi Seungbum, > > > > > > > do I need to run "mpd" every time before I run "mpiexec"? > > > > No. You shouldn't need to run mpd at all. > > > > From the FAQ: "The mpd process manager has many problems, as well as > > an annoying mpdboot step that is fragile and difficult to use > > correctly. The mpd process manager is deprecated at this point ..." > > > > Perhaps when you typed "mpiexec", you were not really running the > > mpiexec binary that you had just built, but rather some other (really > > old) version that was already lying around on your system? > > > > I'd suggest: > > running "which mpiexec" and "mpiexec --version" > > checking your $PATH > > specifying an absolute pathname to the new mpiexec binary instead > > of just "mpiexec" > > > > Hope this helps, > > Nicolás > > _______________________________________________ > > 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 > > > > _______________________________________________ > > 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 > > <config.log>_______________________________________________ > 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

1 0

Re: [mpich-discuss] libintlc.so.5 not found while configuring
by Seungbum Koo 05 Sep '13

05 Sep '13

It should work. 'icc' command works regardless of 'pwd'. So as 'ifort'. I just programmed Hello World! in both C and FORTRAN and they all compiled well and ran successfully. Even for the intel provided sample c source code(one that is in /intel/sample/). I could compile it and successfully run it. Maybe it's version problem. I'll downgrade intel compiler and see if it works in that case. On Thu, Sep 5, 2013 at 7:09 PM, Antonio J. Peña <apenya(a)mcs.anl.gov> wrote: > ** > > > > Seungbum, > > > > I've checked your configure flags in our testbed. I find no problems even > without the LDFLAGS parameter. Have you tried to compile any other code > with your icc setup? I bet there's something wrong with your icc setup. > Have you executed the iccvars.sh script? (BTW, we use icc 13.1.3). > > > > Antonio > > > > > > On Thursday, September 05, 2013 06:34:08 PM Seungbum Koo wrote: > > Thank you for your advice. But nothing has changed even if I add that line > at the stage of configure. > > So this is what I wrote in the command line. > > > ======================================================================== > sudo /opt/mpich/mpich-3.0.4-source/configure --prefix=/opt/mpich/ > CC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icc > CXX=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icpc > F77=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort > FC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort > LDFLAGS="-L/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64" > --enable-fast=all,O3 --enable-g=dbg,mem,log --enable-shared --with-pm=hydra > 2>&1 | sudo tee log_configure.txt > ================================================================ > > What 'configure' says: > ====================================================== > > ld: warning: libintlc.so.5, needed by > /opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/libifport.so.5, > not found (try using -rpath or -rpath-link) > ====================================================== > > What 'make' says: > > > ================================================================ > ld: warning: libimf.so, needed by > /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using > -rpath or -rpath-link) > ld: warning: libsvml.so, needed by > /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using > -rpath or -rpath-link) > ld: warning: libirng.so, needed by > /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using > -rpath or -rpath-link) > ld: warning: libintlc.so.5, needed by > /opt/mpich/mpich-3.0.4-build/src/mpl/.libs/libmpl.so, not found (try using > -rpath or -rpath-link) > ================================================================ > > Not a single line difference as before. > > > Does it make sense? "libifport.so.5" needs "libintlc.so.5" but they are > in the same directory. And those 'not found' files at the 'make' stage as > well. They are all in > '/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/'. > > Any idea? > > > > Seungbum > > > > _______________________________________________ > 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] libintlc.so.5 not found while configuring
by Antonio J. Peña 05 Sep '13

05 Sep '13

Seungbum, I've checked your configure flags in our testbed. I find no problems even without the LDFLAGS parameter. Have you tried to compile any other code with your icc setup? I bet there's something wrong with your icc setup. Have you executed the iccvars.sh script? (BTW, we use icc 13.1.3). Antonio On Thursday, September 05, 2013 06:34:08 PM Seungbum Koo wrote: Thank you for your advice. But nothing has changed even if I add that line at the stage of configure. So this is what I wrote in the command line. sudo /opt/mpich/mpich-3.0.4-source/configure --prefix=/opt/mpich/ CC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icc CXX=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/icpc F77=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort FC=/opt/intel/composer_xe_2013_sp1.0.080/bin/intel64/ifort LDFLAGS="- L/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64" --enable- fast=all,O3 --enable-g=dbg,mem,log --enable-shared --with-pm=hydra 2>&1 | sudo tee log_configure.txt What 'configure' says: =============================================== ======= ld: warning: libintlc.so.5, needed by /opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/libifport.so.5, not found (try using -rpath or -rpath- link)============================================ ========== What 'make' says: Not a single line difference as before. Does it make sense? "libifport.so.5" needs "libintlc.so.5" but they are in the same directory. And those 'not found' files at the 'make' stage as well. They are all in '/opt/intel/composer_xe_2013_sp1.0.080/compiler/lib/intel64/'. Any idea? Seungbum

1 0