[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Changes to PE Proxy configure.in
|
Hi Dave,
In the case of ORTE and LL (and MPICH2, LSF, etc.), there are headers/
libraries that must be present for the proxy to be built, so the
proxies are not built or installed on systems that do not support
them. PE would be the exception to this.
I guess I'd prefer to have a consistent policy for this, not have some
RM's installed and others not installed. Do you see a benefit in
having the proxy built on a machine that doesn't have PE installed?
If PE is going to be built on all platforms, then there are three
cases that need to be addressed:
1. The poe commend is installed in a non-standard location. Not sure
if this is possible, but the proxy should still work if this is the
case.
2. PE is not installed. If the proxy is built, then it should at least
provide some indication that commands can't be submitted (e.g. the
default queue should be in the STOPPED state).
3. Supports all PTP platforms. This is why I added the check in the
first place, as the proxy does not build on Mac OS X.
Greg
On Jan 28, 2008, at 11:32 AM, Dave Wootton wrote:
Greg
I've gotten legal approval for the next set of code for the PE plugin,
enabling LoadLeveler usage, and am currently checking my code
against CVS
to ensure I don't backlevel anything unintentionally.
One change I'm looking at is the addition of a check for the poe
command,
where the configure script will fail if the poe command can't be
found. Is
there something you found that requires this check? My proxy should
compile regardless of whether PE is installed or not, since I don't
use
any PE headers or libraries in building the proxy. I didn't add an
explicit check for the poe command since I was trying to allow for the
case where PTP code is installed and compiled on some node where PE
was
not installed.
Should I keep the changes to check for the poe command in the
configure.in
script?
Dave
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
