Howard,

I regularly test release candidates against the PGI installations on
NERSC's systems (and sometimes elsewhere).  In fact, have a test of
1.8.4rc2 against pgi-14.4 "in the pipe" right now.

I believe Larry Baker of USGS is also a PGI user (in production, rather
than just testing as I do).

-Paul

On Thu, Dec 11, 2014 at 1:34 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com
> wrote:

> Howard --
>
> One thing I neglected to say -- if libfabric/usnic support on master is
> causing problems for you, you can configure without libfabric:
>
>     ./configure --without-libfabric ...
>
> (which will, of course, also disable anything that requires libfabric)
>
> The intent is that we build things by default so that we can get at least
> smoke testing of as many features as possible -- especially testing that
> they don't interfere with others.  But we tend to put in options to shut
> off such things if they *do* cause problems.  Right now, libfabric is
> causing a few problems for you, so you should feel free to disable it until
> we figure out the integration problems (and if you could send me the
> details, I can have a look at what's going wrong).
>
> I'm sorry; I should have mentioned this earlier, but I assumed you knew
> about it / keep forgetting that you're still kinda new to our community and
> don't know all the conventions that we typically put in place!
>
> My bad.  :-(
>
>
>
> On Dec 11, 2014, at 10:45 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>
> wrote:
>
> > On Dec 11, 2014, at 9:58 AM, Howard Pritchard <hpprit...@gmail.com>
> wrote:
> >
> >> Okay, I'll try to fix things.  problem in opal_datatype_internal.h,
> then a meltdown with libfabric owing to the fact that its probably
> >> only been used in a gnu env.  I'll open an issue on that one and assign
> it to Jeff.
> >
> > Ok.
> >
> > FWIW: I test with gcc and the intel compiler suite.  I do not have a PGI
> license to test with.
> >
> >> I think we should be turning this libfabric build off unless one asks
> for it.
> >
> > Obviously, I disagree.  :-)
> >
> > I'm sorry for the annoyances, but we have long since found out that
> features that are not enabled by default do not get tested in the wild and
> therefore do not get debugged.
> >
> > If you send me the details of the PGI problem, I'll be happy to look in
> to it.
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> >
>
>
> --
> 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/12/16511.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

Reply via email to