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
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
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
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'
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
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
>
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.
