Hello,
  When i try to compile openmpi-1.2.6.tar.bz2 on my computer with ifort 
Compilier.My system is Red Hat4.6 86x64.But some mistakes happen when the 
process of configuring.Mistakes as follows:
$./configure --prefix=~/haowp/opt/openmpi FC=ifort F90=ifort
.........
......
*** GNU libltdl setup
configure: OMPI configuring in opal/libltdl
configure: running /bin/sh './configure'  
'--prefix=/stg/s1p1/users/yuanjm/haowp/opt/openmpi' 'FC=ifort' 'F90=ifort' 
--enable-ltdl-convenience --disable-ltdl-install --enable-shared 
--disable-static --cache-file=/dev/null --srcdir=.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... configure: error: newly created 
file is older than distributed files!
Check your system clock
configure: /bin/sh './configure' *failed* for opal/libltdl
configure: error: Failed to build GNU libltdl.  This usually means that 
something
is incorrectly setup with your environment.  There may be useful information in
opal/libltdl/config.log.  You can also disable GNU libltdl (which will disable
dynamic shared object loading) by configuring with --disable-dlopen.

 
$vi /opml/libltdl/config.log
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE_NAME "libltdl"
#define PACKAGE_TARNAME "libltdl"
#define PACKAGE_VERSION "2.1a"
#define PACKAGE_STRING "libltdl 2.1a"
#define PACKAGE_BUGREPORT "bug-libt...@gnu.org"
configure: exit 1

Thank you for your attention.Hope your reply.
 
 
 
 
                                                         haowp
                                                          Sep.15.2011





At 2011-09-15 07:40:55,kevin.buck...@ecs.vuw.ac.nz wrote:
>> That text message is hard-coded (and apparently out of date); it
>> does not show the current value.
>>
>> I agree that that is misleading. This error message needs to be
>> improved.
>
>OK, good to have that clarified Jeff, cheers.
>
>> This might suggest a hardware issue; let us know what you find.
>
>Very likley to be hardware on the node end.
>
>Have a hardware support call open and have just been and swapped
>everything over - ports, cable, even my socks - but a visible
>problem (one link operating at 1x width and not 4x persists).
>
>Probably not a problem with the OpenMPI stack though it has
>highlighted the error message issue (My external MSc supervisor
>said the project raised more questions than it answered, so I
>guess I am continuing the trend, many years on, in a new field!)
>
>Thanks to all who commented,
>Kevin
>
>-- 
>Kevin M. Buckley                                  Room:  CO327
>School of Engineering and                         Phone: +64 4 463 5971
> Computer Science
>Victoria University of Wellington
>New Zealand
>
>_______________________________________________
>users mailing list
>us...@open-mpi.org
>http://www.open-mpi.org/mailman/listinfo.cgi/users

Reply via email to