Hi Paul,
Yes, that is the minor problem I was referring to. It does in fact
reflect the oldness of CLE 4. The cray pmi 5 and higher is newer
software which probably should never have been installed on
CLE 4, since the alps packaging changed completely between
CLE 4 and 5.
Howard
2014-10-28 14:57 GMT-06:00 Paul Hargrove <phhargr...@lbl.gov>:
> By Howard's definition I guess NERSC's Hopper (XE6) qualifies as "very
> old" at PrgEnv 4.2.34
>
> {hargrove@hopper06 ~}$ pkg-config --cflags cray-pmi
> Package cray-alpslli was not found in the pkg-config search path.
> Perhaps you should add the directory containing `cray-alpslli.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'cray-alpslli', required by 'cray-pmi', not found
>
> -Paul
>
>
> On Tue, Oct 28, 2014 at 1:05 PM, Howard Pritchard <hpprit...@gmail.com>
> wrote:
>
>> Hi Folks,
>>
>> The simplest and best way on cray is to use the pkg-config command.
>> No looking for odd header file names, etc. There is a minor issue
>> with external login nodes running very old (like CLE 4.X) that one has
>> to workaround, but otherwise works well.
>>
>> pkg-config --cflags cray-pmi
>>
>> etc. etc.
>>
>> The pc files for the various cray software packages are suppose to include
>> all dependencies on headers files, libs, etc. from other cay packages.
>>
>> Howard
>>
>>
>>
>>
>> 2014-10-28 13:20 GMT-06:00 Ralph Castain <r...@open-mpi.org>:
>>
>>>
>>> On Oct 28, 2014, at 12:17 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>>
>>> Ralph,
>>>
>>> The Cray's at NERSC have *both* pmi_cray.h and pmi.h (and pmi2.h as
>>> well).
>>>
>>>
>>> I understand that - I was questioning if that is universally true or
>>> not. IF we are guaranteed that nobody with a Cray ever renames pmi_cray.h
>>> to pmi.h, THEN your check will be fine. Otherwise, we can’t trust it.
>>>
>>> And I seem to recall that the earlier Crays, at least, didn’t have this
>>> naming distinction - or at least, not at LANL. Hence my question.
>>>
>>>
>>> That is why I said our configure logic checks for pmi_cray.h *first*.
>>> Sorry if that wasn't clear.
>>>
>>> On NERSC's XE6:
>>>
>>> {hargrove@hopper06 ~}$ ls /opt/cray/pmi/default/include/
>>> pmi2.h pmi_cray_ext.h pmi_cray.h pmi.h pmi_version.h
>>> {hargrove@hopper06 ~}$ rpm -qf /opt/cray/pmi/default/include/pmi_cray.h
>>> cray-libpmi-devel-4.0.1-1.0000.9753.86.3.gem
>>>
>>>
>>> On NERSC's XC30:
>>>
>>> {hargrove@edison08 ~}$ ls /opt/cray/pmi/default/include/
>>> pmi.h pmi2.h pmi_cray.h pmi_cray_ext.h pmi_version.h
>>> {hargrove@edison08 ~}$ rpm -qf /opt/cray/pmi/default/include/pmi_cray.h
>>> cray-libpmi-devel-5.0.5-1.0000.10300.134.8.ari
>>>
>>>
>>> -Paul
>>>
>>> On Tue, Oct 28, 2014 at 12:02 PM, Ralph Castain <r...@open-mpi.org>
>>> wrote:
>>>
>>>>
>>>> On Oct 28, 2014, at 11:59 AM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>>>
>>>>
>>>> On Tue, Oct 28, 2014 at 11:53 AM, Howard Pritchard <hpprit...@gmail.com
>>>> > wrote:
>>>>
>>>>>
>>>>>> We may no longer require those as you have separated the Cray check
>>>>>> out, but the original problem is that we would pickup the Slurm
>>>>>> components
>>>>>> on the Cray because we would find pmi.h
>>>>>>
>>>>>> Oh, I forgot about that .
>>>>>
>>>>
>>>> In GASNet's configure logic we look for "pmi_cray.h" before "pmi.h”.
>>>>
>>>>
>>>> Hmmm…on LANL’s Cray systems, it was still labeled “pmi.h”
>>>>
>>>> So far that has been sufficient to disambiguate the implementations.
>>>> One might also try checking libpmi for Cray's extensions.
>>>>
>>>> -Paul
>>>>
>>>>
>>>> --
>>>> Paul H. Hargrove phhargr...@lbl.gov
>>>> Future Technologies Group
>>>> Computer and Data Sciences 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/2014/10/16114.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/10/16115.php
>>>>
>>>
>>>
>>>
>>> --
>>> Paul H. Hargrove phhargr...@lbl.gov
>>> Future Technologies Group
>>> Computer and Data Sciences 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/2014/10/16116.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/10/16117.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/10/16118.php
>>
>
>
>
> --
> Paul H. Hargrove phhargr...@lbl.gov
> Future Technologies Group
> Computer and Data Sciences 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/2014/10/16123.php
>
