Bug 5128 - GRAM LSF job monitor uses INT32_MAX (undefined on Tru64 Unix)
: GRAM LSF job monitor uses INT32_MAX (undefined on Tru64 Unix)
Status: RESOLVED FIXED
: GRAM
wsrf gram clients
: development
: HP OSF/1
: P3 normal
: 4.0.5
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-03-21 10:57 by
Modified: 2007-03-23 08:51 (History)


Attachments
Define INT*MAX/MIN macros for Tru64 build environment (768 bytes, patch)
2007-03-21 10:58, Jeff Forys
Details
replace INT32_MAX with GLOBUS_I_TIME_INFINITY_SEC for time assignment (946 bytes, patch)
2007-03-21 10:59, Jeff Forys
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-03-21 10:57:37
Tru64 Unix does not define the set of INT*_MAX macros.  As a result,
"ws-gram/job_monitoring/lsf/c/source/seg_lsf_module.c" fails to compile:

> cc: Error: seg_lsf_module.c, line 652:
>     In this statement, "INT32_MAX" is not declared. (undeclared)
>         most_recent_event = (time_t) INT32_MAX;

We've run into this before and, in the past, the fix has been to define all of
the INT*_MAX macros appropriately for Tru64.  This fix is contained within the
first patch.

Alternately, since the usage here is setting a time_t to an infinite value, you
may want to use your "GLOBUS_I_TIME_INFINITY_SEC" rather than "INT32_MAX" in
the assignment (although, maybe the GLOBUS macro is only intended to be used
for interval timers).

At any rate, either one of the attached patches will resolve this problem!

Jeff
------- Comment #1 From 2007-03-21 10:58:24 -------
Created an attachment (id=1212) [details]
Define INT*MAX/MIN macros for Tru64 build environment
------- Comment #2 From 2007-03-21 10:59:17 -------
Created an attachment (id=1213) [details]
replace INT32_MAX with GLOBUS_I_TIME_INFINITY_SEC for time assignment
------- Comment #3 From 2007-03-23 08:51:36 -------
Merged the 2nd patch