[OMPI users] openmpi 1.5 build from rpm fails: --program-prefix now checked in configure

[livelfs]

Hi
this is to report that building openmpi-1.5 from rpm fails on Linux
SLES10sp3 x86_64,
due to  --program-prefix switch use now checked in configure script
delivered with 1.5.

rpm is version 4.4.2-43.36.1

rpmbuild --rebuild SRPMS/openmpi-1.5.0.src.rpm --define
'configure_options  CC="/softs/gcc/4.5.1/bin/gcc
"  CXX="/softs/gcc/4.5.1/bin/g++
"  F77="/softs/gcc/4.5.1/bin/gfortran
"  FC="/softs/gcc/4.5.1/bin/gfortran "
--prefix=/opt/openmpi/1.5.0/gfortran-4.5.1-gcc-4.5.1-BLCR-PBS
  --enable-static --enable-shared
--with-wrapper-ldflags="-Wl,-rpath
-Wl,/opt/openmpi/1.5.0/gfortran-4.5.1-gcc-4.5.1-BLCR-PBS/lib64
-Wl,-rpath -Wl,/softs/blcr/0.8/lib"
--with-memory-manager=ptmalloc2
--enable-orterun-prefix-by-default --with-openib
  --disable-ipv6 --with-ft=cr
--enable-ft-thread --enable-mpi-threads
--with-blcr=/softs/blcr/0.8
--enable-mpirun-prefix-by-default
--with-tm=/opt/pbs/default
--with-wrapper-libs="-lpthread -lutil -lrt"' --define '_prefix
/opt/openmpi/1.5.0/gfortran-4.5.1-gcc-4.5.1-BLCR-PBS' --define '_name
openmpi_gfortran-4.5.1-gcc-4.5.1-BLCR-PBS' --define '_topdir /scratch'
--define '_unpackaged_files_terminate_build 0' --define
'use_default_rpm_opt_flags 0'

ends with:
[...]
configure: WARNING: *** This configure script does not support
--program-prefix, --program-suffix or --program-transform-name. Users
are recommended to instead use --prefix with a unique directory and make
symbolic links as desired for renaming.
configure: error: *** Cannot continue


In the present environment (SLES10sp3 x86_64, rpm 4.4.2-43.36.1),
rpmbuild --rebuild produces and execs a temporary shell script calling
configure
with an *empty* --program-prefix switch (--program-prefix=).

It works with openmpi 1.4.3
but configure script from openmpi 1.5 is more picky about using
--program-prefix, --program-suffix or --program-transform-name:

#  diff /usr/src/packages/SOURCES/openmpi-1.5/configure
/usr/src/packages/SOURCES/openmpi-1.4.3/configure | grep program-prefix
< # Suggestion from Paul Hargrove to disable --program-prefix and
< { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: *** This
configure script does not support --program-prefix, --program-suffix or
--program-transform-name. Users are recommended to instead use --prefix
with a unique directory and make symbolic links as desired for
renaming." >&5
< $as_echo "$as_me: WARNING: *** This configure script does not support
--program-prefix, --program-suffix or --program-transform-name. Users
are recommended to instead use --prefix with a unique directory and make
symbolic links as desired for renaming." >&2;}

If I remove the new control on --program-prefix in openmpi-1.5 configure
script, the 1.5 build becomes OK.

Regards,
Stephane Rouberol

Re: [OMPI users] openmpi 1.5 build from rpm fails: --program-prefix now checked in configure

[livelfs]

>Thanks for the report. Someone reported pretty much the same issue to
me off-list a few days ago for RHEL5.
>
>It looks like RHEL5 / 6 ship with Autoconf 2.63, and have a
/usr/lib/rpm/macros that defines %configure to include options such as
--program-suffix. We bootstrapped Open MPI v1.5 with Autoconf 2.65,
which does not understand the --program-suffix option.
>
>I don't know why AC 2.65 dropped the --program-suffix option, but this
seems to be where we are.
>
>I've emailed a contact at Red Hat asking for advice on what to do here
-- I can't imagine Open MPI is the only package in this situation.

I confirm troubles on SLES10sp3 x86_64 come from
/usr/lib/rpm/macros (from rpm 4.4.2-43.36.1 package)
which includes:
#  grep program-prefix /usr/lib/rpm/macros
--program-prefix=%{?_program_prefix} \\\

Regards,
Stephane Rouberol

>
>On Oct 19, 2010, at 4:47 AM, livelfs wrote:
>
>> Hi
>> this is to report that building openmpi-1.5 from rpm fails on Linux
>> SLES10sp3 x86_64,
>> due to --program-prefix switch use now checked in configure script
>> delivered with 1.5.
>>
>> rpm is version 4.4.2-43.36.1
>>
>> rpmbuild --rebuild SRPMS/openmpi-1.5.0.src.rpm --define
>> 'configure_options CC="/softs/gcc/4.5.1/bin/gcc
>> " CXX="/softs/gcc/4.5.1/bin/g++
>> " F77="/softs/gcc/4.5.1/bin/gfortran
>> " FC="/softs/gcc/4.5.1/bin/gfortran "
>> --prefix=/opt/openmpi/1.5.0/gfortran-4.5.1-gcc-4.5.1-BLCR-PBS
>> --enable-static --enable-shared
>> --with-wrapper-ldflags="-Wl,-rpath
>> -Wl,/opt/openmpi/1.5.0/gfortran-4.5.1-gcc-4.5.1-BLCR-PBS/lib64
>> -Wl,-rpath -Wl,/softs/blcr/0.8/lib"
>> --with-memory-manager=ptmalloc2
>> --enable-orterun-prefix-by-default --with-openib
>> --disable-ipv6 --with-ft=cr
>> --enable-ft-thread --enable-mpi-threads
>> --with-blcr=/softs/blcr/0.8
>> --enable-mpirun-prefix-by-default
>> --with-tm=/opt/pbs/default
>> --with-wrapper-libs="-lpthread -lutil -lrt"' --define '_prefix
>> /opt/openmpi/1.5.0/gfortran-4.5.1-gcc-4.5.1-BLCR-PBS' --define '_name
>> openmpi_gfortran-4.5.1-gcc-4.5.1-BLCR-PBS' --define '_topdir /scratch'
>> --define '_unpackaged_files_terminate_build 0' --define
>> 'use_default_rpm_opt_flags 0'
>>
>> ends with:
>> [...]
>> configure: WARNING: *** This configure script does not support
>> --program-prefix, --program-suffix or --program-transform-name. Users
>> are recommended to instead use --prefix with a unique directory and make
>> symbolic links as desired for renaming.
>> configure: error: *** Cannot continue
>>
>>
>> In the present environment (SLES10sp3 x86_64, rpm 4.4.2-43.36.1),
>> rpmbuild --rebuild produces and execs a temporary shell script calling
>> configure
>> with an *empty* --program-prefix switch (--program-prefix=).
>>
>> It works with openmpi 1.4.3
>> but configure script from openmpi 1.5 is more picky about using
>> --program-prefix, --program-suffix or --program-transform-name:
>>
>> # diff /usr/src/packages/SOURCES/openmpi-1.5/configure
>> /usr/src/packages/SOURCES/openmpi-1.4.3/configure | grep program-prefix
>> < # Suggestion from Paul Hargrove to disable --program-prefix and
>> < { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: *** This
>> configure script does not support --program-prefix, --program-suffix or
>> --program-transform-name. Users are recommended to instead use --prefix
>> with a unique directory and make symbolic links as desired for
>> renaming." >&5
>> < $as_echo "$as_me: WARNING: *** This configure script does not support
>> --program-prefix, --program-suffix or --program-transform-name. Users
>> are recommended to instead use --prefix with a unique directory and make
>> symbolic links as desired for renaming." >&2;}
>>
>> If I remove the new control on --program-prefix in openmpi-1.5 configure
>> script, the 1.5 build becomes OK.
>>
>> Regards,
>> Stephane Rouberol
>>
>> ___
>> users mailing list
>> users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>--
>Jeff Squyres
>jsquyres_at_[hidden]
>For corporate legal information go to:
>http://www.cisco.com/web/about/doing_business/legal/cri/

[OMPI users] Building openmpi from src rpm: rpmbuild --rebuild errors with 'cpio: MD5 sum mismatch' (since openmpi 1.4.5)

[livelfs]

Hi
Since 1.4.5 openmpi release, it is no longer possible to build openmpi 
binary with rpmbuild --rebuild if system rpm package version is 4.4.x, 
like in SLES10, SLES11, RHEL/CentOS 5.x.


For instance, on CentOS 5.8 x86_64 with rpm 4.4.2.3-28.el5_8:

[root@horizon _tmp]# rpmbuild --rebuild openmpi-1.4.5-1.src.rpm
Installing openmpi-1.4.5-1.src.rpm
warning: user jsquyres does not exist - using root
error: unpacking of archive failed on file 
/usr/src/redhat/SPECS/openmpi-1.4.5.spec;4fc65c74: cpio: MD5 sum mismatch

error: openmpi-1.4.5-1.src.rpm cannot be installed

Apparently this problem is due to lack of support of SHA-256 in rpm 4.4.x

Googling suggests
  rpmbuild -bs \
   --define "_source_filedigest_algorithm md5" \
   --define "_binary_filedigest_algorithm md5" \
   package.spec
should be used to produce openmpi src rpms and avoid the problem.

Please note that
- rpmbuild works OK on RHEL/CentOS 5.x with openmpi-1.4.4-1.src.rpm and 
all previous versions
- rpmbuild works OK on with all openmpi versions with rpm 4.8.x from 
RHEL/CentOS 6.x

- this is of course not blocking, since I successfully tested 2 workarounds
1) install package with --nomd5, then rpmbuild -ba 
2) repackage with "old" rpm:
rpm2cpio to extract spec file + sources tar
rpmbuild -bs  to produce new src rpm
Then rpmbuild --rebuild is OK

Regards,
Stephane Rouberol
--- Begin Message ---

Hi
Since 1.4.5 openmpi release, it is no longer possible to build openmpi 
binary with rpmbuild --rebuild if system rpm package version is 4.4.x, 
like in SLES10, SLES11, RHEL/CentOS 5.x.


For instance, on CentOS 5.8 with rpm 4.4.2.3-28.el5_8:

[root@horizon _tmp]# rpmbuild --rebuild openmpi-1.4.5-1.src.rpm
Installing openmpi-1.4.5-1.src.rpm
warning: user jsquyres does not exist - using root
error: unpacking of archive failed on file 
/usr/src/redhat/SPECS/openmpi-1.4.5.spec;4fc65c74: cpio: MD5 sum mismatch

error: openmpi-1.4.5-1.src.rpm cannot be installed

Apparently this problem is due to lack of support of SHA-256 in rpm 4.4.x

Googling suggests
  rpmbuild -bs \
   --define "_source_filedigest_algorithm md5" \
   --define "_binary_filedigest_algorithm md5" \
   package.spec
should be used to produce openmpi src rpms and avoid the problem.

Please note that
- rpmbuild works OK on RHEL/CentOS 5.x with openmpi-1.4.4-1.src.rpm and 
all previous versions
- rpmbuild works OK on with all openmpi versions with rpm 4.8.x from 
RHEL/CentOS 6.x

- I successfully tested 2 workarounds
1) install package with --nomd5, then rpmbuild -ba 
2) repackage with "old" rpm
rpm2cpio to extract spec file + sources tar
rpmbuild -bs  to produce new src rpm
Then rpmbuild --rebuild is OK

Regards,
Stephane Rouberol

--- End Message ---

Re: [OMPI users] Building openmpi from src rpm: rpmbuild --rebuild errors with 'cpio: MD5 sum mismatch' (since openmpi 1.4.5)

[livelfs]

On 06/01/2012 02:25 PM, livelfs wrote:

On May 31, 2012, at 2:04 AM, livelfs wrote:


Since 1.4.5 openmpi release, it is no longer possible to build
openmpi binary with rpmbuild --rebuild if system rpm package version is
4.4.x, like >in SLES10, SLES11, RHEL/CentOS 5.x.

For instance, on CentOS 5.8 x86_64 with rpm 4.4.2.3-28.el5_8:

[root@horizon _tmp]# rpmbuild --rebuild openmpi-1.4.5-1.src.rpm
Installing openmpi-1.4.5-1.src.rpm
warning: user jsquyres does not exist - using root
error: unpacking of archive failed on file
/usr/src/redhat/SPECS/openmpi-1.4.5.spec;4fc65c74: cpio: MD5 sum mismatch
error: openmpi-1.4.5-1.src.rpm cannot be installed

Apparently this problem is due to lack of support of SHA-256 in rpm 4.4.x


Mmmm.  I wonder if this corresponds to me upgrading my cluster (where I
make the SRPM) from RHEL5 to RHEL6.  I'll bet it does.  :-\


+1


Just curious -- do you know if there's a way I can make an
RHEL5-friendly SRPM on my RHEL6 cluster?  I seem to have RPM 4.8.0 on my
RHEL6 >machines.


As I mentioned in my previous mail, what about testing

rpmbuild --define "_source_filedigest_algorithm md5"  \
   --define "_binary_filedigest_algorithm md5"

on RHEL6 ?


Or, better yet, perhaps I should be producing the SRPM on the official
OMPI build machine (i.e., where we make our tarballs), which is still
back at >RHEL4.  I'm not quite sure how it evolved that we make tarballs
in tightly controlled conditions, but the SRPM is just made by hand on
my cluster >(which is subject to upgrades, etc.).  Hrm. :-\


What puzzles me is that I could not reproduce the problem using
rpmbuild -bs
on CentOS 6.2 with rpm-4.8.0-19.el6_2.1.x86_64
Perhaps a rpm config difference between RHEL and CentOS ?

Anyway, using rpm 4.4.x to produce src rpms seems to me to be the safest 
path


Regards,
Stephane Rouberol


--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] Building openmpi from src rpm: rpmbuild --rebuild errors with 'cpio: MD5 sum mismatch' (since openmpi 1.4.5)

[livelfs]

On Jun 1, 2012, at 2:17 PM, livelfs wrote:


 Just curious -- do you know if there's a way I can make an
 RHEL5-friendly SRPM on my RHEL6 cluster?  I seem to have RPM 4.8.0 on my
 RHEL6>machines.


 As I mentioned in my previous mail, what about testing

 rpmbuild --define "_source_filedigest_algorithm md5"  \
   --define "_binary_filedigest_algorithm md5"


Oops -- I missed that.  Can you try the -2 SRPM found here:

http://www.open-mpi.org/~jsquyres/unofficial/



Hi again
I found only one SRPM: 
http://www.open-mpi.org/~jsquyres/unofficial/openmpi-1.6-2.src.rpm


I successfully tested
rpmbuild --rebuild openmpi-1.6-2.src.rpm
(passed GZDIO step) on x86_64 CentOS5.8, CentOS6.2, and SLES10sp2.
Good!

Regards,
Stephane Rouberol

Re: [OMPI users] Building openmpi from src rpm: rpmbuild --rebuild errors with 'cpio: MD5 sum mismatch' (since openmpi 1.4.5)

[livelfs]

> Hi again
> I found only one SRPM: 
http://www.open-mpi.org/~jsquyres/unofficial/openmpi-1.6-2.src.rpm 


>
> I successfully tested
> rpmbuild --rebuild openmpi-1.6-2.src.rpm
> (passed GZDIO step) on x86_64 CentOS5.8, CentOS6.2, and SLES10sp2.
> Good!


>Excellent -- many thanks for the help.

>I updated the following SRPMs on the OMPI site:

>- 1.6
>- 1.4.5
>- 1.5.5

>All of these were built with new versions of RPM and defaulted to SHA1 
checksums. So I build them with the MD5 checksums and put out -2 
versions of those SRPMs.



Thanx a lot!
1.4.5 & 1.5.5 are indeed in -2 on OMPI site and I tested them OK.

But as of now 1.6 seems to be still in non working -1 version though.

Regards,
Stephane Rouberol

[OMPI users] 1.2.1 configure bug report: set CC variable may produce broken *wrapper-data.txt

[livelfs]

Hi all

I have observed a regression between 1.2 and 1.2.1

if CC is assigned an absolute path (i.e. export
CC=/opt/gcc/gcc-3.4.4/bin/gcc like in attached logs),
the */tools/wrappers/*-wrapper-data.txt files
produced by configure script have then a broken libs macro definition:

libs=-lmpi -lopen-rte -lopen-pal   -ldl   dummy ranlib

instead of
libs=-lmpi -lopen-rte -lopen-pal   -ldl   -Wl,--export-dynamic -lnsl
-lutil -lm -ldl

Regards,
Stephane Rouberol



ompi-output.tar.gz
Description: GNU Zip compressed data

Re: [OMPI users] AlphaServers & OpenMPI

[livelfs]

Rob wrote:
>
> Hi,
>
> One more question with respect to running OpenMPI on my AlphaServers
> and other PCs in my lab.
>
> Version 1.2.1 fails to build on the AlphaServers, but miraculously the
> nightly snapshot openmpi-1.3a1r14639 works fine. Now, I need to have
> OpenMPI set up on a production cluster, but openmpi-1.3XXX is under
> active development.
> What is recommended to use in this case for my cluster system?
> I would prefer that the appropriate fix also be applied to 1.2.x series,
> so that I can rely on the a stable version ?
>
> Thanks,
> Rob.
> *** 
> *
>
> 
> Be a better Heartthrob. Get better relationship answers
> from
> someone who knows.
> Yahoo! Answers - Check it out.
> 
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
your 1.2.1 build error seems to be the one I bumped into.
Try to avoid to give an absolute path to CC macro when you run configure
(check the archives)