garrick at usc.edu
Thu Jul 8 12:41:33 MDT 2010
On Thu, Jul 08, 2010 at 11:57:32AM -0400, Baer, Troy alleged:
> On Thu, 2010-07-08 at 08:40 -0700, Garrick Staples wrote:
> > On Thu, Jul 08, 2010 at 09:53:15AM -0400, Baer, Troy alleged:
> > > 2. There appears to be no way to disable whatever feature turns on the
> > > C compiler flag -DUSEJOBCREATE -- is that intentional?
> > It's intentional in that when ataufer added the USEJOBCREATE lines to
> > configure.ac he didn't add conditional code.
> > Is this a problem? It was obviously assumed that everyone on Cray would want to
> > use the job_create feature.
> > Also, we have the path hard-coded to /opt/cray/job/default/lib64. Is that Ok?
> > I'm sure I would have complained about that at the time.
> Well, given that it's an SGI machine where this is being picked up,
> perhaps /opt/cray/whatever is not always the right location. On my UV,
> the equivalent path is /usr/lib64.
But what about defing USEJOBCREATE in the first place? Are you trying to
disable that code, or is this just something you noticed?
Do all machines with job_create(), require its use?
Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California
Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20100708/416614ea/attachment.bin
More information about the torquedev