Mike --

If this is Autotools related, then it should be possible to replicate on RHEL 
6.x machines.

What versions of all the autootools are you using?

Autoconf
Automake
Libtool
m4


On Jul 24, 2014, at 8:39 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:

> it seems autotools related:
> it tries to create link in "hooks" subfolder which does not present.
> 
> 
> linux:/var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/mpi
>  # ls -al
> total 248
> drwxr-xr-x 1 hpcuser mtl     474 Jul 24 15:32 .
> drwxr-xr-x 1 hpcuser mtl    1058 Jul 24 15:16 ..
> -rw-r--r-- 1 root    root  93739 Jul 24 15:16 Makefile
> -rw-r--r-- 1 hpcuser mtl    1191 Jul 24 08:49 Makefile.am
> -rw-r--r-- 1 hpcuser mtl  105110 Jul 24 08:53 Makefile.in
> lrwxrwxrwx 1 root    root     88 Jul 24 15:20 vt_unify.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify.cc
> lrwxrwxrwx 1 root    root     93 Jul 24 15:20 vt_unify_defs.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_defs.cc
> lrwxrwxrwx 1 root    root     98 Jul 24 15:20 vt_unify_defs_recs.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_defs_recs.cc
> lrwxrwxrwx 1 root    root    101 Jul 24 15:20 vt_unify_events_stats.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_events_stats.cc
> lrwxrwxrwx 1 root    root     97 Jul 24 15:20 vt_unify_handlers.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_handlers.cc
> lrwxrwxrwx 1 root    root     94 Jul 24 15:20 vt_unify_hooks.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_hooks.cc
> -rw-r--r-- 1 hpcuser mtl     574 Jul 24 08:49 vt_unify_lib.h
> lrwxrwxrwx 1 root    root     96 Jul 24 15:20 vt_unify_markers.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_markers.cc
> -rw-r--r-- 1 hpcuser mtl    1104 Jul 24 08:49 vt_unify_mpi.h
> lrwxrwxrwx 1 root    root     93 Jul 24 15:20 vt_unify_sync.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_sync.cc
> lrwxrwxrwx 1 root    root     94 Jul 24 15:20 vt_unify_tkfac.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_tkfac.cc
> lrwxrwxrwx 1 root    root     95 Jul 24 15:20 vt_unify_usrcom.cc -> 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/vt_unify_usrcom.cc
> linux:/var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/mpi
>  # make
>   CXX      libvt_mpi_unify_la-vt_unify.lo
>   CXX      libvt_mpi_unify_la-vt_unify_defs.lo
>   CXX      libvt_mpi_unify_la-vt_unify_defs_recs.lo
>   CXX      libvt_mpi_unify_la-vt_unify_events_stats.lo
>   CXX      libvt_mpi_unify_la-vt_unify_handlers.lo
>   CXX      libvt_mpi_unify_la-vt_unify_hooks.lo
>   CXX      libvt_mpi_unify_la-vt_unify_markers.lo
>   CXX      libvt_mpi_unify_la-vt_unify_sync.lo
>   CXX      libvt_mpi_unify_la-vt_unify_tkfac.lo
>   CXX      libvt_mpi_unify_la-vt_unify_usrcom.lo
> ln -s 
> /var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/hooks/vt_unify_hooks_base.cc
>  hooks/vt_unify_hooks_base.cc
> ln: failed to create symbolic link 'hooks/vt_unify_hooks_base.cc': No such 
> file or directory
> Makefile:1593: recipe for target 'hooks/vt_unify_hooks_base.cc' failed
> make: *** [hooks/vt_unify_hooks_base.cc] Error 1
> linux:/var/tmp/OFED_topdir/BUILD/openmpi-1.8.2rc2/ompi/contrib/vt/vt/tools/vtunify/mpi
>  # make V=1
> 
> 
> 
> On Thu, Jul 24, 2014 at 2:45 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
> wrote:
> I just tried it myself -- "make distcheck" succeeds for both a nightly 
> tarball (openmpi-1.8.2rc2r32302) and in a git or svn checkout on RHEL 6.5.
> 
> I do not have easy access to RHEL 7 or SLES 12 beta.
> 
> Can someone analyze this and figure out what the difference is?
> 
> 
> 
> On Jul 24, 2014, at 6:21 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
> wrote:
> 
> > I am getting reports of similar failures from Cisco QA.  They have 
> > clean/fresh checkouts of the OMPI tree.
> >
> > It does not seem to happen on RHEL 6.5, but does happen on RHEL 7 and SLES 
> > 12 (beta).
> >
> > What's the difference?
> >
> >
> > On Jul 24, 2014, at 6:12 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:
> >
> >> this is a command line we use:
> >>
> >> cd ./contrib/dist/linux
> >> ./contrib/dist/make_tarball -greekonly
> >> rpmbuild --rebuild  --define '_topdir /var/tmp//OFED_topdir' --define 
> >> 'dist %{nil}' --target x86_64 --define '_name openmpi' --define 
> >> 'mpi_selector /usr/bin/mpi-selector' --define 'use_mpi_selector 1' 
> >> --define 'install_shell_scripts 1' --define 'shell_scripts_basename 
> >> mpivars' --define '_usr /usr' --define 'ofed 0' --define '_prefix 
> >> /usr/mpi/gcc/openmpi-1.8.2rc2' --define '_defaultdocdir 
> >> /usr/mpi/gcc/openmpi-1.8.2rc2' --define '_mandir %{_prefix}/share/man' 
> >> --define '_datadir %{_prefix}/share' --define 'mflags -j 4' --define 
> >> 'configure_options    --with-fca=/opt/mellanox/fca 
> >> --with-hcoll=/opt/mellanox/hcoll  --with-mxm=/opt/mellanox/mxm  
> >> --with-knem=/opt/knem-1.1.1.90mlnx 
> >> --with-platform=contrib/platform/mellanox/optimized  ' --define 
> >> 'use_default_rpm_opt_flags 1' openmpi-1.8.2rc2-1.src.rpm
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Thu, Jul 24, 2014 at 11:58 AM, Bert Wesarg <bert.wes...@tu-dresden.de> 
> >> wrote:
> >> On 07/24/2014 10:15 AM, Mike Dubman wrote:
> >> the problem occurs when build is started from src.rpm (and probably from
> >> tarball as well):
> >>
> >> try make distcheck and use src tree from tarball.
> >>
> >> I did now make distcheck from the rc2 tarball, and it all worked. I don't 
> >> know what the srpm does differently than an ./configure && make though.
> >>
> >> Bert
> >>
> >>
> >>
> >>
> >> On Thu, Jul 24, 2014 at 10:57 AM, Bert Wesarg <bert.wes...@tu-dresden.de>
> >> wrote:
> >>
> >>
> >> --
> >> Dipl.-Inf. Bert Wesarg
> >> wiss. Mitarbeiter
> >>
> >> Technische Universität Dresden
> >> Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
> >> 01062 Dresden
> >> Tel.: +49 (351) 463-42451
> >> Fax: +49 (351) 463-37773
> >> E-Mail: bert.wes...@tu-dresden.de
> >>
> >>
> >> _______________________________________________
> >> devel mailing list
> >> de...@open-mpi.org
> >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >> Link to this post: 
> >> http://www.open-mpi.org/community/lists/devel/2014/07/15238.php
> >>
> >> _______________________________________________
> >> devel mailing list
> >> de...@open-mpi.org
> >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >> Link to this post: 
> >> http://www.open-mpi.org/community/lists/devel/2014/07/15239.php
> >
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to: 
> > http://www.cisco.com/web/about/doing_business/legal/cri/
> >
> > _______________________________________________
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post: 
> > http://www.open-mpi.org/community/lists/devel/2014/07/15240.php
> 
> 
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/07/15242.php
> 
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/07/15244.php


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

Reply via email to