them to the following format:
openmpi-${BRANCHNAME}-${MMDD}-${SHORTHASH}.tar.bz2
Here's what last night's tarballs would have looked like with that scheme:
openmpi-master-20161017-bd1b6fe.tar.bz2
openmpi-v2.0.x-20161017-a66f3e2.tar.bz2
openmpi-v2.x-20161017-
On 18/10/16 07:17, Jeff Squyres (jsquyres) wrote:
> NOTE: It may be desirable to add HHMM in there; it's not common, but
> *sometimes* we do make more than one snapshot in a day (e.g., if one
> snapshot is borked, so we fix it and then generate another
> snapshot).
If it's been happened before th
Folks,
this is a follow up on a question from the users ML
is there any reason why plugins do not depend on the main openmpi libs
(libopen-pal.so and libopen-rte.so, libompi.so and liboshmem.so if needed) ?
i guess that would solve the issue here without having to use RTLD_GLOBAL.
Cheers,
t night's tarballs would have looked like with that scheme:
openmpi-master-20161017-bd1b6fe.tar.bz2
openmpi-v2.0.x-20161017-a66f3e2.tar.bz2
openmpi-v2.x-20161017-56991c6.tar.bz2
Optionally, we could put a HHMM timestamp in there for finer granularity.
MORE DETAIL
===
We use
#x27;s the
>> most recent on each branch:
>>
>> - Master: openmpi-v2.x-dev-3019-gbd1b6fe.tar.bz2
>> - v2.0.x: openmpi-v2.0.1-93-g97511a1.tar.bz2
>> - v2.x: openmpi-v2.0.1-203-g56991c6.tar.bz2
>>
>> I propose changing them to the following format:
>&
