You don't mention what kind of hang you get...'simple hang' or 'total
power off hang'...
Thing's getting hung in a dynamic view always make me suspicious of
having an inappropriate path:
You must not have any PATH pointing into the dynamic view, unless that
path comes *after* the path to CC binaries...
We used to run things from the view using a path and it wasn't until
someone happened to have something like this that things went haywire:
PATH=\path\into\view;\path\to\CC
This is a surefire way to get a big hang, cause this will cause CC
process to loop...basically, 'hmm, some process tries to read into the
view...ok, doesn't seem that I have the proper CC dll's loaded, better
do that first by checking the path for them'. And so it goes, spinning
out of control...
The simple remedy for that is:
PATH=\path\to\CC;\path\into\view
Now, this was in CC 3.1 or something like it so maybe there are steps to
guard against it...but in case this is what you suffer from...
ken1
> -----Original Message-----
> From: Peter.Mueller1@mch.siemens.de
> [mailto:Peter.Mueller1@mch.siemens.de
> Sent: Monday, July 02, 2001 04:01
> To: cciug@rational.com
> Subject: [cciug] [Win2k] Using nmake in omake makefile hangs with MS
> Link
>
>
>
> Hi,
>
> for various reasons, I'm currently investigating some
> performance issues. On
> is build timing. For a project I've rewritten the build script to use
> Makefiles (the original build script is based on .bat files
> and is highly
> intertwined with VSS ...).
>
> Anyway, I've tried to extract build information from the .bat
> and to include
> them my Makefile (I want to be as equal as possible, hence, I
> want to use
> the same set of commands to build the software). There are
> build scripts,
> which invoke nmake. So, I have the following "call stack":
>
> omake -f MyMakefile ==> nmake -f ProjectMakefileForComponent
> ==> MS Link
>
> When running this in a dynamic view using local view storage (ie. view
> storage is on my machine, not on a server) the LINK process hangs.
>
> I've tracked down the problem to the fact, that when deleting
> generated
> files (ie. doing a remove on view privates) everything works fine.
>
> During the build process the following file types are created:
>
> .DEF
> .exp
> .lib
> .obj
> .pdb
> .res
> .vrc
> .vxd
>
> I do not know all of them :-)
>
> Well ... I would appreciate any hints you have. Note: The
> build works fine
> using remote view storage. This leads me to the assumption
> that local view
> storage and its associated processes might not be compatible
> with MS LINK.
>
> Thanks for your time
>
> Peter
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> can also
> unsubscribe
>
> http://clearcase.rational.com/cciug/mailing_list.html
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:48 EDT