[mpich-discuss] Configuration issues for mpich2-1.5b2

Bharath Ramesh bramesh at vt.edu
Tue Jan 29 08:45:24 CST 2013


On Tue, Jan 29, 2013 at 08:40:37AM -0600, Dave Goodell wrote:
> On Jan 29, 2013, at 8:14 AM CST, Bharath Ramesh wrote:
> 
> > On Tue, Jan 29, 2013 at 08:08:29AM -0600, Dave Goodell wrote:
> >> The relevant config.log files would help here.  You can grab all of them for us with:
> >> 
> >> find . -name "config.log" | xargs tar czf config.logs.tar.gz
> >> 
> >> from your build directory.  Then just send us "config.logs.tar.gz".
> > 
> > I have attached the tar ball of all the config.log from the build
> > directory.
> 
> 
> Your LD_LIBRARY_PATH (or other library path configuration mechanism) is configured incorrectly:
> 
> ----8<----
> configure:16164: checking size of void *
> configure:16169: gcc -o conftest    -O2   -I/home/bramesh/ARC/apps/build/mpich-3.0.1/src/mpl/include -I/home/bramesh/ARC/apps/build/mpich-3.0.1/src/mpl/include -I/home/bramesh/ARC/apps/build/mpich-3.0.1/src/openpa/src -I/home/bramesh/ARC/apps/build/mpich-3.0.1/src/openpa/src -I/home/bramesh/ARC/apps/build/mpich-3.0.1/src/mpi/romio/include -I/opt/torque/torque/include  -lnsl -L/opt/torque/torque/lib64 -L/opt/torque/torque/lib conftest.c -ltorque  >&5
> configure:16169: $? = 0
> configure:16169: ./conftest
> ./conftest: error while loading shared libraries: libtorque.so.2: cannot open shared object file: No such file or directory
> configure:16169: $? = 127
> configure: program exited with status 127
> configure: failed program was:
> […]
> ----8<----

I was able to build it by passing the actual path to torque as
part of CFLAGS rpath. I will figure out why the LD_LIBRARY_PATH
isnt configured properly. Thanks for the help and helping me
resolve this issue.

-- 
Bharath
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4553 bytes
Desc: not available
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20130129/02b59da8/attachment.bin>


More information about the discuss mailing list