Bug 609647

Is the problem that you really are having issues compiling/linking code, or that 'mpicc --showme:link' is not working for you?
I'm asking because you're not running (MPICH2's) mpicc with the correct argument. I guess you're using to openmpi, to see the compile or link info used by MPICH2's mpicc, your run it with '-link-info' or 'compile-info' arguments;
"mpicc -link-info" or "mpicc -compile-info" or just "mpicc -info".

mpich2.x86_64 1.2.1p1-2.fc13 works quite well for me (without manually exporting LD_LIBRARY_PATH env like you did above).

mpicc -info
/usr/bin/ld: cannot find -lmpich

I cannot compile actual codes: I have tried 
http://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-lite-3.1-p3.tar.gz
and 
https://computation.llnl.gov/casc/hypre/download/hypre-2.6.0b_reg.html
and both have failed with the same error: 
/usr/bin/ld: cannot find -lmpich(

In reply to comment #1)
> Is the problem that you really are having issues compiling/linking code, or
> that 'mpicc --showme:link' is not working for you?
> I'm asking because you're not running (MPICH2's) mpicc with the correct
> argument. I guess you're using to openmpi, to see the compile or link info used
> by MPICH2's mpicc, your run it with '-link-info' or 'compile-info' arguments;
> "mpicc -link-info" or "mpicc -compile-info" or just "mpicc -info".
> 
> mpich2.x86_64 1.2.1p1-2.fc13 works quite well for me (without manually
> exporting LD_LIBRARY_PATH env like you did above).

Can you attach the build logs for the failed compilations?

Created attachment 428093 [details]
hypre config log

Created attachment 428094 [details]
petsc configure log

It is not related just to mpich2. I get the exactly same error using openmpi.x86_64   1.4.1-4.fc13

(In reply to comment #6)
> It is not related just to mpich2. I get the exactly same error using
> openmpi.x86_64   1.4.1-4.fc13    

I've been thinking about this issue, but can't figure it out at all yet. It seems to me that something might have messed up with your system configuration somewhere or a package (eg. environment-module or glibc).
Are you loading some custom scripts on start-up?

No. It's a fresh install of FC13, with nothing special, and all current updates. 

(In reply to comment #7)
> (In reply to comment #6)
> > It is not related just to mpich2. I get the exactly same error using
> > openmpi.x86_64   1.4.1-4.fc13    
> 
> I've been thinking about this issue, but can't figure it out at all yet. It
> seems to me that something might have messed up with your system configuration
> somewhere or a package (eg. environment-module or glibc).
> Are you loading some custom scripts on start-up?

I have found the source of the problem. 

ld is trying to find libmpich.so , which is not available in mpich2 rpm. On my other system, FC12, where it works, I do have a soft link libmpich.so -> libmpich.so.1.2 , but I do not remember how it got there. 

If I add on FC13 in /usr/lib64/mpich2/lib
ln -s libmpich.so.1.2 libmpich.so
now I get a different error
/usr/bin/ld: cannot find -lopa

So, how to get all the missing soft links? And why there are not in the rpm?

Problem solved! There were missing packages openmpi-devel.x86_64 and mpich2-devel.x86_64 

Thanks for trying to help!

Good to know you found the solution. I'm still intrigued by how it needs the *-devel sub-package to work. mpicc (and mpicxx,mpif*) used to be packaged in the -devel sub-package.