naughtont -> naughtont3
Thanks,
--tjn
_
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
On Wed, 10 Sep 2014, Jeff Squy
Hi Jeff,
Cool, no worries. I just didn't want to forget.
Thanks,
--tjn
_
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
-exising
functionality. If you have a "${project}/config/" directory. This
appends the "-I ${project}/config/" to the autoreconf list.
If you do not have a "${project}/config/" dir, there is no change.
Again, I hope that gives more context/descripti
? Or does it replace/override the default?
Thanks Jeff for forwarding info to devel list to get broader feedback, and
to Ralph for providing the suggestion.
--tjn
_
Thomas Naughton naught
ogen.pl (r28241) and
it does indeed generate the Makefiles for that directory. So it does seem
reasonable that if autogen.pl processes the directory for Makefile stuff*,
that it should process it for the "frameworks.h" entry.
I'll revert that part of the changeset to previous functionality.
Hi,
It looks like an auto-generated 'install-sh' was accidentally added to SVN
under libevent in OPAL:
ompi-trunk/opal/mca/event/libevent2021/libevent/install-sh
Ok, to remove it?
--tjn
_
Thomas Naughton
Hi Ralph,
Does the version in AM_INIT_AUTOMAKE in configure.ac also need to be
increased? It currently shows 1.11.
Thanks,
--tjn
_
Thomas Naughton naught...@ornl.gov
Research
h" file?
I understand the general motivation for the API change but it is less clear
to me how the information previously defined in the header changes (or does
not change)?
Thanks,
--tjn
_____
Thomas Naughton
Hi Ralph,
OK, thanks for clarification and code pointers.
I'll update "rte.h" to reflect the updates.
Thanks,
--tjn
_____
Thomas Naughton naught...@ornl.gov
Research
Hi Ralph,
This component does provide a alternate reference for the ompi-rte
framework. But if it is unused (unmaintained), it seems less useful in
practice. I'll post another RFC for related request.
--tjn
_
Thomas
stem. This will also
provide an alternate component to ORTE, which was motivation for PMI
component in related RFC. We build/test nightly and it occasionally
catches ompi-rte abstraction violations, etc.
Thomas
_
Thomas Naug
Inline comments ... way at the bottom. ;-)
--tjn
_
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
On Tue, 27 May 2014
Sure, if its helpful I can join a call.
--tjn
_
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
On Tue, 27 May 2014, Ralph
_
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
On Thu, 29 May 2014, Jeff Squyres (jsquyres) wrote:
I refrained from speaking up on this thread because I
nks,
--tjn
_____
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
___
devel mailing list
devel@lists.open-mpi
_
Thomas Naughton naught...@ornl.gov
Research Associate (865) 576-4184
On Fri, 24 Feb 2017, r...@open-mpi.org wrote:
On Feb 24, 2017, at 11:57 AM, Thomas Naughton <naught...@ornl.gov> wrote:
Hi,
We're trying to
out in future (based on
discussion on call today).
I guess the main point of interest would be to have some method for
launching the DVM scenario with OMPI. Another option could be to rename
the binary in OMPI?
Thanks,
--tjn
___
Hi Ralph,
Is the 'prun' tool required to launch the DVM?
I know that at some point things shifted to use 'prun' and didn't require
the URI on command-line, but I've not tested in few months.
Thanks,
--tjn
_
Thomas
On Tue, 5 Jun 2018, r...@open-mpi.org wrote:
On Jun 5, 2018, at 11:59 AM, Thomas Naughton wrote:
Hi Ralph,
All it means is that PRRTE users must be careful to have PRRTE before OMPI in
their path values. Otherwise, they get the wrong “prun” and it fails. I suppose
I could update
/openpmix
(v1.1.3-2128-gb94e261)
52d498811f19be5306bd55b8433024733d3b589a prrte (dev-30165-g52d4988)
beaker:$
--tjn
_
Thomas Naughton naught...@ornl.gov
Research Associate
20 matches
Mail list logo