Thanks for all the responses,
But, Actually we are trying to run the clearmake on three different
platforms, which are ClearCase installed, from the same view and from the
same directory, but the target Directories are different.
Correct me if I am wrong, that means Clearmake cannot handle Concurrent
processes in a single view, eventhough the target directories are different.
Thanks in advance,
Ramesh
-----Original Message-----
From: Paul D. Smith [mailto:pausmith@nortelnetworks.com
Sent: Wednesday, February 09, 2000 1:22 PM
To: Douglas B. Robinson
Cc: pausmith@nortelnetworks.com; jangareddi, ramesh;
'cciug'
Subject: Re: [cciug] Concurrent Clearmake Warnings
under Unix
%% "Douglas B. Robinson" <robinson@cup.hp.com> writes:
dbr> At 09:04 AM 2/9/00 -0500, Paul D. Smith wrote:
>> %% "jangareddi, ramesh" <jangareddi_ramesh@emc.com>
writes:
jr> When I run several clearmakes at the same time --
different Unix
jr> machines/telnet-windows -- I frequently get the
following warning:
jr> clearmake: Warning: Error closing CR cache file
.cmake.state - Stale remove file handle
>> You absolutely cannot run multiple separate invocations
of clearmake in
>> the same directory at the same time. You can't even do
this with
>> regular make, although normal make is stateless so the
chance of actual
>> conflict is much less--but still there.
dbr> While I agree that this situation is non-optimal, it
can and does
dbr> arise in ways that are perfectly acceptible. For
example, having
dbr> two makefiles in a single directory, one that only
does meta-work
dbr> before invoking the other, is a technique that can be
used to
dbr> solve certain problems that may not lend themselves
to other
dbr> solutions (e.g. you're not allowed to change some
vender supplied
dbr> makefile due to "incredibly stupid contract
agreements"). As
dbr> long as the two makefiles do not try to build the
same targets
dbr> then all is well and the *Warning:* above can be
ignored. Yes,
dbr> this is an advanced topic but the blanket "you
absolutely cannot
dbr> run" is an overstatement.
When I wrote "separate invocations" I did that specifically
to mean I
_wasn't_ talking about a recursive make situation (that is,
running a
submake from within another make). Obviously that's
fine--it's done all
the time. I probably should have made that clearer.
I'm not intimately familiar with the uses of the
.cmake.state cache
file, but we've had a lot of situations here where two
separate
clearmake invocations in the same directory have caused
unnecessary
rebuilds, etc. even when they ostensibly weren't updating
the same
target file. Changing these invocations to serial and/or
using -J to
get parallelism instead always fixed these problems.
I can't see any need to ever do this, so I prefer to play it
safe, KISS,
and just say "not allowed, ever".
--
----------------------------------------------------------------------------
--- Paul D. Smith <psmith@baynetworks.com> Network Management Development "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ---------------------------------------------------------------------------- --- These are my opinions---Nortel Networks takes no responsibility for them. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:09 EDT