[Kfwdev] Building in AFS

[Jeffrey Altman]

Kevin Koch wrote:
>
> I was asked politely to duplicate Jeff’s build in an AFS directory. 
>
Thank you for doing so. 
>
> Here’s what I did:
>
>  
>
>     * Copy \user\j\a\jaltman\Public\KFW\bkw to
>       \user\k\p\kpkoch\Public\bkw.
>     * Replace bkw.pl with rolled back version, so build will be in
>       directory specified in passN-cfg.xml instead of in c:\KfW.  I
>       have since updated svn so bkw.pl in the repository is rolled back.
>     * Change pass1-cfg.xml & pass2-cfg.xml to use kserver and to not
>       sign.  [I can’t sign.]
>     * Change build-afs.cmd to use my directory; specify /USER on the
>       bkw command lines; use == instead of eq so that second half will
>       run.
>
This is required for using cmd as the wrapper shell.  You may have
noticed that I execute each "perl bkw.pl..." prefaced with "cmd.exe
/c".  This is so that other shells with more flexible command parsers
could be used.  My favorite is JPSoftware's 4NT because it is aware of
AFS and can use UNIX path notation.   However, Microsoft's PowerShell
also is UNC aware and works just fine. 

Seeing that this caused you a portability problem I replaced the
notation with

    IF ERRORLEVEL 0 <cmd>

because that is portable across all of the shells.
>
>  
>
> The first build completes and the results are in
> \user\k\p\kpkoch\Public\bkw\test\dist.  The second build fails and I’m
> looking at it.
>
>  
>
> To use the modified build-afs.cmd, you will need to:
>
>  
>
>     * Copy \user\k\p\kpkoch\Public\bkw without subdirectories.
>     * Change kpkoch to your own username in build-afs.cmd.
>     * Disconnect X: after the first try, or net use will fail.
>
Its ok for NET USE to fail.  Its cosmetic.  I just put it there to make
sure that the drive letter was defined.
>
>     * Make sure to delete any pismere directory after the first try,
>       or build-afs.cmd will hang at the first bkw.pl.
>
As you discovered, "find" is walking the tree.  I see you committed a
patch for that.  
Thank you.

To improve the build performance from AFS I suggest you increase the
cache size to 800MB or so.  See
http://www.secure-endpoints.com/oafw/relnotes.htm#_Toc154229465.  The
default size is smaller than the working set of the KFW build.

Jeffrey Altman



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3355 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.mit.edu/pipermail/kfwdev/attachments/20070419/85befe5f/attachment.bin