Re: [OMPI users] Cofigure(?) problem building /1.5.3 on ScientificLinux6.0
Hello Gus, Ralph, Jeff
a very late answer for this - just found it in my mailbox.
Would "cp -rp" help?
(To preserve time stamps, instead of "cp -r".)
Yes, the root of the evil were the time stamps. 'cp -a' is the magic
wand. Many thanks for your help, and I should wear sackcloth and
ashes... :-/
Best,
Paul
Anyway, since 1.2.8 here I build 5, sometimes more versions,
all from the same tarball, but on separate build directories,
as Jeff suggests.
[VPATH] Works for me.
My two cents.
Gus Correa
Jeff Squyres wrote:
Ah -- Ralph pointed out the relevant line to me in your first mail
that I initially missed:
In each case I build 16 versions at all (4 compiler * 32bit/64bit *
support for multithreading ON/OFF). The same error arise in all 16
versions.
Perhaps you should just expand the tarball once and then do VPATH
builds...?
Something like this:
tar xf openmpi-1.5.3.tar.bz2
cd openmpi-1.5.3
mkdir build-gcc
cd build-gcc
../configure blah..
make -j 4
make install
cd ..
mkdir build-icc
../configure CC=icc CXX=icpc FC=ifort F77=ifort ..blah.
make -j 4
make install
cd ..
etc.
This allows you to have one set of source and have N different builds
from it. Open MPI uses the GNU Autotools correctly to support this
kind of build pattern.
On Jul 22, 2011, at 2:37 PM, Jeff Squyres wrote:
Your RUNME script is a *very* strange way to build Open MPI. It
starts with a massive copy:
cp -r /home/pk224850/OpenMPI/openmpi-1.5.3/AUTHORS
/home/pk224850/OpenMPI/openmpi-1.5.3/CMakeLists.txt <...much
snipped...> .
Why are you doing this kind of copy? I suspect that the GNU
autotools' timestamps are getting all out of whack when you do this
kind of copy, and therefore when you run "configure", it tries to
re-autogen itself.
To be clear: when you expand OMPI from a tarball, you shouldn't need
the GNU Autotools installed at all -- the tarball is pre-bootstrapped
exactly to avoid you needing to use the Autotools (much less any
specific version of the Autotools).
I suspect that if you do this:
-
tar xf openmpi-1.5.3.tar.bz2
cd openmpi-1.5.3
./configure etc.
-
everything will work just fine.
On Jul 22, 2011, at 11:12 AM, Paul Kapinos wrote:
Dear OpenMPI volks,
currently I have a problem by building the version 1.5.3 of OpenMPI on
Scientific Linux 6.0 systems, which seem vor me to be a configuration
problem.
After the configure run (which seem to terminate without error code),
the "gmake all" stage produces errors and exits.
Typical is the output below.
Fancy: the 1.4.3 version on same computer can be build with no special
trouble. Both the 1.4.3 and 1.5.3 versions can be build on other
computer running CentOS 5.6.
In each case I build 16 versions at all (4 compiler * 32bit/64bit *
support for multithreading ON/OFF). The same error arise in all 16
versions.
Can someone give a hint about how to avoid this issue? Thanks!
Best wishes,
Paul
Some logs and configure are downloadable here:
https://gigamove.rz.rwth-aachen.de/d/id/2jM6MEa2nveJJD
The configure line is in RUNME.sh, the
logs of configure and build stage in log_* files; I also attached the
config.log file and the configure itself (which is the standard from
the
1.5.3 release).
##
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
/tmp/pk224850/linuxc2_11254/openmpi-1.5.3mt_linux64_gcc/config/missing
--run aclocal-1.11 -I config
sh: config/ompi_get_version.sh: No such file or directory
/usr/bin/m4: esyscmd subprocess failed
configure.ac:953: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
m4_defun'd
config/ompi_mca.m4:37: OMPI_MCA is expanded from...
configure.ac:953: the top level
configure.ac:953: warning: AC_COMPILE_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
../../lib/autoconf/specific.m4:386: AC_USE_SYSTEM_EXTENSIONS is
expanded
from...
opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:152:
HWLOC_SETUP_CORE_AFTER_C99 is expanded from...
../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:22: HWLOC_SETUP_CORE is
expanded from...
opal/mca/paffinity/hwloc/configure.m4:40: MCA_paffinity_hwloc_CONFIG is
expanded from...
config/ompi_mca.m4:540: MCA_CONFIGURE_M4_CONFIG_COMPONENT is expanded
from...
config/ompi_mca.m4:326: MCA_CONFIGURE_FRAMEWORK is expanded from...
config/ompi_mca.m4:247: MCA_CONFIGURE_PROJECT is expanded from...
configure.ac:953: warning: AC_RUN_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
--
Dipl.-Inform. Paul Kapinos - High Performance Computing,
RWTH Aachen University, Center for Computing and Communication
Seffenter Weg 23, D 52074 Aachen (Germany)
Tel: +49 241/80-24915
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
Re: [OMPI users] Cofigure(?) problem building /1.5.3 on ScientificLinux6.0
Hi
Would "cp -rp" help?
(To preserve time stamps, instead of "cp -r".)
Anyway, since 1.2.8 here I build 5, sometimes more versions,
all from the same tarball, but on separate build directories,
as Jeff suggests.
[VPATH] Works for me.
My two cents.
Gus Correa
Jeff Squyres wrote:
Ah -- Ralph pointed out the relevant line to me in your first mail that I
initially missed:
In each case I build 16 versions at all (4 compiler * 32bit/64bit *
support for multithreading ON/OFF). The same error arise in all 16 versions.
Perhaps you should just expand the tarball once and then do VPATH builds...?
Something like this:
tar xf openmpi-1.5.3.tar.bz2
cd openmpi-1.5.3
mkdir build-gcc
cd build-gcc
../configure blah..
make -j 4
make install
cd ..
mkdir build-icc
../configure CC=icc CXX=icpc FC=ifort F77=ifort ..blah.
make -j 4
make install
cd ..
etc.
This allows you to have one set of source and have N different builds from it.
Open MPI uses the GNU Autotools correctly to support this kind of build pattern.
On Jul 22, 2011, at 2:37 PM, Jeff Squyres wrote:
Your RUNME script is a *very* strange way to build Open MPI. It starts with a
massive copy:
cp -r /home/pk224850/OpenMPI/openmpi-1.5.3/AUTHORS
/home/pk224850/OpenMPI/openmpi-1.5.3/CMakeLists.txt <...much snipped...> .
Why are you doing this kind of copy? I suspect that the GNU autotools' timestamps are
getting all out of whack when you do this kind of copy, and therefore when you run
"configure", it tries to re-autogen itself.
To be clear: when you expand OMPI from a tarball, you shouldn't need the GNU
Autotools installed at all -- the tarball is pre-bootstrapped exactly to avoid
you needing to use the Autotools (much less any specific version of the
Autotools).
I suspect that if you do this:
-
tar xf openmpi-1.5.3.tar.bz2
cd openmpi-1.5.3
./configure etc.
-
everything will work just fine.
On Jul 22, 2011, at 11:12 AM, Paul Kapinos wrote:
Dear OpenMPI volks,
currently I have a problem by building the version 1.5.3 of OpenMPI on
Scientific Linux 6.0 systems, which seem vor me to be a configuration
problem.
After the configure run (which seem to terminate without error code),
the "gmake all" stage produces errors and exits.
Typical is the output below.
Fancy: the 1.4.3 version on same computer can be build with no special
trouble. Both the 1.4.3 and 1.5.3 versions can be build on other
computer running CentOS 5.6.
In each case I build 16 versions at all (4 compiler * 32bit/64bit *
support for multithreading ON/OFF). The same error arise in all 16 versions.
Can someone give a hint about how to avoid this issue? Thanks!
Best wishes,
Paul
Some logs and configure are downloadable here:
https://gigamove.rz.rwth-aachen.de/d/id/2jM6MEa2nveJJD
The configure line is in RUNME.sh, the
logs of configure and build stage in log_* files; I also attached the
config.log file and the configure itself (which is the standard from the
1.5.3 release).
##
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
/tmp/pk224850/linuxc2_11254/openmpi-1.5.3mt_linux64_gcc/config/missing
--run aclocal-1.11 -I config
sh: config/ompi_get_version.sh: No such file or directory
/usr/bin/m4: esyscmd subprocess failed
configure.ac:953: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
m4_defun'd
config/ompi_mca.m4:37: OMPI_MCA is expanded from...
configure.ac:953: the top level
configure.ac:953: warning: AC_COMPILE_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
../../lib/autoconf/specific.m4:386: AC_USE_SYSTEM_EXTENSIONS is expanded
from...
opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:152:
HWLOC_SETUP_CORE_AFTER_C99 is expanded from...
../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:22: HWLOC_SETUP_CORE is
expanded from...
opal/mca/paffinity/hwloc/configure.m4:40: MCA_paffinity_hwloc_CONFIG is
expanded from...
config/ompi_mca.m4:540: MCA_CONFIGURE_M4_CONFIG_COMPONENT is expanded
from...
config/ompi_mca.m4:326: MCA_CONFIGURE_FRAMEWORK is expanded from...
config/ompi_mca.m4:247: MCA_CONFIGURE_PROJECT is expanded from...
configure.ac:953: warning: AC_RUN_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
--
Dipl.-Inform. Paul Kapinos - High Performance Computing,
RWTH Aachen University, Center for Computing and Communication
Seffenter Weg 23, D 52074 Aachen (Germany)
Tel: +49 241/80-24915
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Cofigure(?) problem building /1.5.3 on ScientificLinux6.0
Ah -- Ralph pointed out the relevant line to me in your first mail that I
initially missed:
> In each case I build 16 versions at all (4 compiler * 32bit/64bit *
> support for multithreading ON/OFF). The same error arise in all 16 versions.
Perhaps you should just expand the tarball once and then do VPATH builds...?
Something like this:
tar xf openmpi-1.5.3.tar.bz2
cd openmpi-1.5.3
mkdir build-gcc
cd build-gcc
../configure blah..
make -j 4
make install
cd ..
mkdir build-icc
../configure CC=icc CXX=icpc FC=ifort F77=ifort ..blah.
make -j 4
make install
cd ..
etc.
This allows you to have one set of source and have N different builds from it.
Open MPI uses the GNU Autotools correctly to support this kind of build pattern.
On Jul 22, 2011, at 2:37 PM, Jeff Squyres wrote:
> Your RUNME script is a *very* strange way to build Open MPI. It starts with
> a massive copy:
>
> cp -r /home/pk224850/OpenMPI/openmpi-1.5.3/AUTHORS
> /home/pk224850/OpenMPI/openmpi-1.5.3/CMakeLists.txt <...much snipped...> .
>
> Why are you doing this kind of copy? I suspect that the GNU autotools'
> timestamps are getting all out of whack when you do this kind of copy, and
> therefore when you run "configure", it tries to re-autogen itself.
>
> To be clear: when you expand OMPI from a tarball, you shouldn't need the GNU
> Autotools installed at all -- the tarball is pre-bootstrapped exactly to
> avoid you needing to use the Autotools (much less any specific version of the
> Autotools).
>
> I suspect that if you do this:
>
> -
> tar xf openmpi-1.5.3.tar.bz2
> cd openmpi-1.5.3
> ./configure etc.
> -
>
> everything will work just fine.
>
>
> On Jul 22, 2011, at 11:12 AM, Paul Kapinos wrote:
>
>> Dear OpenMPI volks,
>> currently I have a problem by building the version 1.5.3 of OpenMPI on
>> Scientific Linux 6.0 systems, which seem vor me to be a configuration
>> problem.
>>
>> After the configure run (which seem to terminate without error code),
>> the "gmake all" stage produces errors and exits.
>>
>> Typical is the output below.
>>
>> Fancy: the 1.4.3 version on same computer can be build with no special
>> trouble. Both the 1.4.3 and 1.5.3 versions can be build on other
>> computer running CentOS 5.6.
>>
>> In each case I build 16 versions at all (4 compiler * 32bit/64bit *
>> support for multithreading ON/OFF). The same error arise in all 16 versions.
>>
>> Can someone give a hint about how to avoid this issue? Thanks!
>>
>> Best wishes,
>>
>> Paul
>>
>>
>> Some logs and configure are downloadable here:
>> https://gigamove.rz.rwth-aachen.de/d/id/2jM6MEa2nveJJD
>>
>> The configure line is in RUNME.sh, the
>> logs of configure and build stage in log_* files; I also attached the
>> config.log file and the configure itself (which is the standard from the
>> 1.5.3 release).
>>
>>
>> ##
>>
>>
>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
>> /tmp/pk224850/linuxc2_11254/openmpi-1.5.3mt_linux64_gcc/config/missing
>> --run aclocal-1.11 -I config
>> sh: config/ompi_get_version.sh: No such file or directory
>> /usr/bin/m4: esyscmd subprocess failed
>>
>>
>>
>> configure.ac:953: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
>> m4_defun'd
>> config/ompi_mca.m4:37: OMPI_MCA is expanded from...
>> configure.ac:953: the top level
>> configure.ac:953: warning: AC_COMPILE_IFELSE was called before
>> AC_USE_SYSTEM_EXTENSIONS
>> ../../lib/autoconf/specific.m4:386: AC_USE_SYSTEM_EXTENSIONS is expanded
>> from...
>> opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:152:
>> HWLOC_SETUP_CORE_AFTER_C99 is expanded from...
>> ../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
>> opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:22: HWLOC_SETUP_CORE is
>> expanded from...
>> opal/mca/paffinity/hwloc/configure.m4:40: MCA_paffinity_hwloc_CONFIG is
>> expanded from...
>> config/ompi_mca.m4:540: MCA_CONFIGURE_M4_CONFIG_COMPONENT is expanded
>> from...
>> config/ompi_mca.m4:326: MCA_CONFIGURE_FRAMEWORK is expanded from...
>> config/ompi_mca.m4:247: MCA_CONFIGURE_PROJECT is expanded from...
>> configure.ac:953: warning: AC_RUN_IFELSE was called before
>> AC_USE_SYSTEM_EXTENSIONS
>>
>>
>>
>>
>> --
>> Dipl.-Inform. Paul Kapinos - High Performance Computing,
>> RWTH Aachen University, Center for Computing and Communication
>> Seffenter Weg 23, D 52074 Aachen (Germany)
>> Tel: +49 241/80-24915
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate
Re: [OMPI users] Cofigure(?) problem building /1.5.3 on ScientificLinux6.0
Your RUNME script is a *very* strange way to build Open MPI. It starts with a
massive copy:
cp -r /home/pk224850/OpenMPI/openmpi-1.5.3/AUTHORS
/home/pk224850/OpenMPI/openmpi-1.5.3/CMakeLists.txt <...much snipped...> .
Why are you doing this kind of copy? I suspect that the GNU autotools'
timestamps are getting all out of whack when you do this kind of copy, and
therefore when you run "configure", it tries to re-autogen itself.
To be clear: when you expand OMPI from a tarball, you shouldn't need the GNU
Autotools installed at all -- the tarball is pre-bootstrapped exactly to avoid
you needing to use the Autotools (much less any specific version of the
Autotools).
I suspect that if you do this:
-
tar xf openmpi-1.5.3.tar.bz2
cd openmpi-1.5.3
./configure etc.
-
everything will work just fine.
On Jul 22, 2011, at 11:12 AM, Paul Kapinos wrote:
> Dear OpenMPI volks,
> currently I have a problem by building the version 1.5.3 of OpenMPI on
> Scientific Linux 6.0 systems, which seem vor me to be a configuration
> problem.
>
> After the configure run (which seem to terminate without error code),
> the "gmake all" stage produces errors and exits.
>
> Typical is the output below.
>
> Fancy: the 1.4.3 version on same computer can be build with no special
> trouble. Both the 1.4.3 and 1.5.3 versions can be build on other
> computer running CentOS 5.6.
>
> In each case I build 16 versions at all (4 compiler * 32bit/64bit *
> support for multithreading ON/OFF). The same error arise in all 16 versions.
>
> Can someone give a hint about how to avoid this issue? Thanks!
>
> Best wishes,
>
> Paul
>
>
> Some logs and configure are downloadable here:
> https://gigamove.rz.rwth-aachen.de/d/id/2jM6MEa2nveJJD
>
> The configure line is in RUNME.sh, the
> logs of configure and build stage in log_* files; I also attached the
> config.log file and the configure itself (which is the standard from the
> 1.5.3 release).
>
>
> ##
>
>
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
> /tmp/pk224850/linuxc2_11254/openmpi-1.5.3mt_linux64_gcc/config/missing
> --run aclocal-1.11 -I config
> sh: config/ompi_get_version.sh: No such file or directory
> /usr/bin/m4: esyscmd subprocess failed
>
>
>
> configure.ac:953: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
> m4_defun'd
> config/ompi_mca.m4:37: OMPI_MCA is expanded from...
> configure.ac:953: the top level
> configure.ac:953: warning: AC_COMPILE_IFELSE was called before
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:386: AC_USE_SYSTEM_EXTENSIONS is expanded
> from...
> opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:152:
> HWLOC_SETUP_CORE_AFTER_C99 is expanded from...
> ../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
> opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:22: HWLOC_SETUP_CORE is
> expanded from...
> opal/mca/paffinity/hwloc/configure.m4:40: MCA_paffinity_hwloc_CONFIG is
> expanded from...
> config/ompi_mca.m4:540: MCA_CONFIGURE_M4_CONFIG_COMPONENT is expanded
> from...
> config/ompi_mca.m4:326: MCA_CONFIGURE_FRAMEWORK is expanded from...
> config/ompi_mca.m4:247: MCA_CONFIGURE_PROJECT is expanded from...
> configure.ac:953: warning: AC_RUN_IFELSE was called before
> AC_USE_SYSTEM_EXTENSIONS
>
>
>
>
> --
> Dipl.-Inform. Paul Kapinos - High Performance Computing,
> RWTH Aachen University, Center for Computing and Communication
> Seffenter Weg 23, D 52074 Aachen (Germany)
> Tel: +49 241/80-24915
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI users] Cofigure(?) problem building /1.5.3 on ScientificLinux6.0
Hi Ralph,
Higher rev levels of the autotools are required for the 1.5 series - are you at
the right ones? See
http://www.open-mpi.org/svn/building.php
Many thanks for the link.
Short test, and it's out: autoconf version on our release is too old. We
have 2.63 and needed ist 2.65.
I will trigger our admins...
Best wishes,
Paul
m4 (GNU M4) 1.4.13 (OK)
autoconf (GNU Autoconf) 2.63 (Need: 2.65, NOK)
automake (GNU automake) 1.11.1 (OK)
ltmain.sh (GNU libtool) 2.2.6b (OK)
On Jul 22, 2011, at 9:12 AM, Paul Kapinos wrote:
Dear OpenMPI volks,
currently I have a problem by building the version 1.5.3 of OpenMPI on
Scientific Linux 6.0 systems, which seem vor me to be a configuration
problem.
After the configure run (which seem to terminate without error code),
the "gmake all" stage produces errors and exits.
Typical is the output below.
Fancy: the 1.4.3 version on same computer can be build with no special
trouble. Both the 1.4.3 and 1.5.3 versions can be build on other
computer running CentOS 5.6.
In each case I build 16 versions at all (4 compiler * 32bit/64bit *
support for multithreading ON/OFF). The same error arise in all 16 versions.
Can someone give a hint about how to avoid this issue? Thanks!
Best wishes,
Paul
Some logs and configure are downloadable here:
https://gigamove.rz.rwth-aachen.de/d/id/2jM6MEa2nveJJD
The configure line is in RUNME.sh, the
logs of configure and build stage in log_* files; I also attached the
config.log file and the configure itself (which is the standard from the
1.5.3 release).
##
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
/tmp/pk224850/linuxc2_11254/openmpi-1.5.3mt_linux64_gcc/config/missing
--run aclocal-1.11 -I config
sh: config/ompi_get_version.sh: No such file or directory
/usr/bin/m4: esyscmd subprocess failed
configure.ac:953: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
m4_defun'd
config/ompi_mca.m4:37: OMPI_MCA is expanded from...
configure.ac:953: the top level
configure.ac:953: warning: AC_COMPILE_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
../../lib/autoconf/specific.m4:386: AC_USE_SYSTEM_EXTENSIONS is expanded
from...
opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:152:
HWLOC_SETUP_CORE_AFTER_C99 is expanded from...
../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:22: HWLOC_SETUP_CORE is
expanded from...
opal/mca/paffinity/hwloc/configure.m4:40: MCA_paffinity_hwloc_CONFIG is
expanded from...
config/ompi_mca.m4:540: MCA_CONFIGURE_M4_CONFIG_COMPONENT is expanded
from...
config/ompi_mca.m4:326: MCA_CONFIGURE_FRAMEWORK is expanded from...
config/ompi_mca.m4:247: MCA_CONFIGURE_PROJECT is expanded from...
configure.ac:953: warning: AC_RUN_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
--
Dipl.-Inform. Paul Kapinos - High Performance Computing,
RWTH Aachen University, Center for Computing and Communication
Seffenter Weg 23, D 52074 Aachen (Germany)
Tel: +49 241/80-24915
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Dipl.-Inform. Paul Kapinos - High Performance Computing,
RWTH Aachen University, Center for Computing and Communication
Seffenter Weg 23, D 52074 Aachen (Germany)
Tel: +49 241/80-24915
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [OMPI users] Cofigure(?) problem building /1.5.3 on ScientificLinux6.0
Higher rev levels of the autotools are required for the 1.5 series - are you at
the right ones? See
http://www.open-mpi.org/svn/building.php
On Jul 22, 2011, at 9:12 AM, Paul Kapinos wrote:
> Dear OpenMPI volks,
> currently I have a problem by building the version 1.5.3 of OpenMPI on
> Scientific Linux 6.0 systems, which seem vor me to be a configuration
> problem.
>
> After the configure run (which seem to terminate without error code),
> the "gmake all" stage produces errors and exits.
>
> Typical is the output below.
>
> Fancy: the 1.4.3 version on same computer can be build with no special
> trouble. Both the 1.4.3 and 1.5.3 versions can be build on other
> computer running CentOS 5.6.
>
> In each case I build 16 versions at all (4 compiler * 32bit/64bit *
> support for multithreading ON/OFF). The same error arise in all 16 versions.
>
> Can someone give a hint about how to avoid this issue? Thanks!
>
> Best wishes,
>
> Paul
>
>
> Some logs and configure are downloadable here:
> https://gigamove.rz.rwth-aachen.de/d/id/2jM6MEa2nveJJD
>
> The configure line is in RUNME.sh, the
> logs of configure and build stage in log_* files; I also attached the
> config.log file and the configure itself (which is the standard from the
> 1.5.3 release).
>
>
> ##
>
>
> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
> /tmp/pk224850/linuxc2_11254/openmpi-1.5.3mt_linux64_gcc/config/missing
> --run aclocal-1.11 -I config
> sh: config/ompi_get_version.sh: No such file or directory
> /usr/bin/m4: esyscmd subprocess failed
>
>
>
> configure.ac:953: warning: OMPI_CONFIGURE_SETUP is m4_require'd but not
> m4_defun'd
> config/ompi_mca.m4:37: OMPI_MCA is expanded from...
> configure.ac:953: the top level
> configure.ac:953: warning: AC_COMPILE_IFELSE was called before
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:386: AC_USE_SYSTEM_EXTENSIONS is expanded
> from...
> opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:152:
> HWLOC_SETUP_CORE_AFTER_C99 is expanded from...
> ../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
> opal/mca/paffinity/hwloc/hwloc/config/hwloc.m4:22: HWLOC_SETUP_CORE is
> expanded from...
> opal/mca/paffinity/hwloc/configure.m4:40: MCA_paffinity_hwloc_CONFIG is
> expanded from...
> config/ompi_mca.m4:540: MCA_CONFIGURE_M4_CONFIG_COMPONENT is expanded
> from...
> config/ompi_mca.m4:326: MCA_CONFIGURE_FRAMEWORK is expanded from...
> config/ompi_mca.m4:247: MCA_CONFIGURE_PROJECT is expanded from...
> configure.ac:953: warning: AC_RUN_IFELSE was called before
> AC_USE_SYSTEM_EXTENSIONS
>
>
>
>
> --
> Dipl.-Inform. Paul Kapinos - High Performance Computing,
> RWTH Aachen University, Center for Computing and Communication
> Seffenter Weg 23, D 52074 Aachen (Germany)
> Tel: +49 241/80-24915
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
