I had fixed it in my local tree but not yet pushed to my github branch; I was 
waiting to see what happened w.r.t. your failure on the NERSC machine.

I pushed the fix up to my branch now; do you want a new tarball?


> On Feb 2, 2015, at 5:56 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
> 
> Jeff,
> 
> Looks like you didn't hit all the un-guarded references to lt_dladvise.
> Specifically you missed a struct decl:
> 
> /[....]/openmpi-libltdl-linux-x86_64-gcc/openmpi-gitclone/opal/util/lt_interface.c:25:8:
>  error: unknown type name 'lt_dladvise'
> 
> -Paul
> 
> 
> On Sat, Jan 31, 2015 at 4:44 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
> wrote:
> Looks like the lt_interface.c code didn't properly use the lt_dladvise #if. 
> How did that ever work, I wonder?
> 
> Fixed now.  On to your second finding...
> 
> 
> > On Jan 30, 2015, at 7:42 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
> >
> > Not meeting with the greatest of success.
> > This is a report of just the first (of at least 2) failure modes I am 
> > seeing.
> >
> > On a Scientific Linux 5.5. (RHEL-5.5 clone like CentOS) I get a build 
> > failure described below.
> > At least Solaris-11 and a few other linux systems (including RHAS-4.4) are 
> > also failing in what appears to be the same manner.
> > I am sure there are more, but I am aborting this round of testing at this 
> > point.
> >
> > I again await a new tarball with a less broken-by-default behavior.
> >
> > -Paul
> >
> >
> > The configure output includes
> > checking ltdl.h usability... yes
> > checking ltdl.h presence... yes
> > checking for ltdl.h... yes
> > looking for library without search path
> > checking for lt_dlopen in -lltdl... yes
> > checking for lt_dladvise_init... no
> > configure: WARNING: *********************************************
> > configure: WARNING: Could not find lt_dladvise_init in libltdl
> > configure: WARNING: This could mean that your libltdl version
> > configure: WARNING: is old.  If you could upgrade, that would be great.
> > configure: WARNING: *********************************************
> > checking for lt_dladvise... no
> >
> > However, it looks like opal/utill/lt_interface.c is still attempting to 
> > call lt_dladvise:
> > PGC-S-0040-Illegal use of symbol, lt_dladvise 
> > (/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-libltdl-linux-x86_64-pgi-12.10/openmpi-gitclone/opal/util/lt_interface.c:
> >  25)
> > PGC-W-0156-Type not specified, 'int' assumed 
> > (/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-libltdl-linux-x86_64-pgi-12.10/openmpi-gitclone/opal/util/lt_interface.c:
> >  25)
> > PGC/x86-64 Linux 12.10-0: compilation completed with severe errors
> >
> > The put of "libtool --version" says "1.5.22" and we have libltdl.so.3.1.4.
> > However, the rpm database is not readable, preventing me from checking a 
> > package version associated with the libltdl.
> >
> > The failing Solaris-11/x86-64 system says 1.5.22 without any ambiguity:
> > $ pkg info libltdl | grep Version
> >        Version: 1.5.22
> >
> >
> > -Paul
> >
> >
> >
> >
> >
> >
> >
> > On Fri, Jan 30, 2015 at 3:51 PM, Jeff Squyres (jsquyres) 
> > <jsquy...@cisco.com> wrote:
> > New tarball posted (same location).  Now featuring 100% fewer "make check" 
> > failures.
> >
> >     http://www.open-mpi.org/~jsquyres/unofficial/
> >
> >
> > > On Jan 30, 2015, at 5:14 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
> > > wrote:
> > >
> > > Shame on me for not running "make check".
> > >
> > > Fixing...
> > >
> > >
> > >> On Jan 30, 2015, at 4:58 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
> > >>
> > >> Jeff,
> > >>
> > >> I ran on just one (mac OSX 10.8) system first as a "smoke test".
> > >> It encountered the failure show below on "make check" at which point I 
> > >> decided not to test 60+ platforms.
> > >> Please advise how I should proceed (best guess is wait for a new 
> > >> tarball).
> > >>
> > >> -Paul
> > >>
> > >> Making check in test
> > >> Making check in support
> > >> make  libsupport.a
> > >>  CC       components.o
> > >> /Users/Paul/OMPI/openmpi-libltdl-macos10.8-x86-clang/openmpi-gitclone/test/support/components.c:27:10:
> > >>  fatal error: 'opal/libltdl/ltdl.h' file not found
> > >> #include "opal/libltdl/ltdl.h"
> > >>         ^
> > >>
> > >>
> > >> On Fri, Jan 30, 2015 at 1:29 PM, Jeff Squyres (jsquyres) 
> > >> <jsquy...@cisco.com> wrote:
> > >> On Jan 30, 2015, at 2:46 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
> > >>>
> > >>> If I had new enough autotools to autogen on this old system then I 
> > >>> wouldn't have asked about libltdl from libtool-1.4.  So, please *do* 
> > >>> generate a tarball and I will test (on *all* of my systems).
> > >>
> > >> Sweet, thank you.  I just posted a tarball here:
> > >>
> > >>    http://www.open-mpi.org/~jsquyres/unofficial/
> > >>
> > >> --
> > >> 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/2015/01/16854.php
> > >>
> > >>
> > >>
> > >> --
> > >> Paul H. Hargrove                          phhargr...@lbl.gov
> > >> Computer Languages & Systems Software (CLaSS) Group
> > >> Computer Science Department               Tel: +1-510-495-2352
> > >> Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
> > >> _______________________________________________
> > >> 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/2015/01/16855.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/2015/01/16856.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/2015/01/16857.php
> >
> >
> >
> > --
> > Paul H. Hargrove                          phhargr...@lbl.gov
> > Computer Languages & Systems Software (CLaSS) Group
> > Computer Science Department               Tel: +1-510-495-2352
> > Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
> > _______________________________________________
> > 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/2015/01/16858.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/2015/01/16863.php
> 
> 
> 
> -- 
> Paul H. Hargrove                          phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department               Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
> _______________________________________________
> 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/2015/02/16887.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