Followup to problem, a colleague asked:
>You mentioned that you had adjusted permissions on the file, but the 
>permissions have be correct all along the path - you might want to check the 
>parent directories to ensure their permissions are right.

I should have noted originally: I did check the whole path. And I did try a 
command prompt run as Administrator. All permissions good, no joy as admin.

>The compiler must have had permission to write the file – I’m guessing CMake 
>copied it somewhere??

No idea what CMake did – that’s part of the problem! The dasm command is:
C:\Progra~2\Dignus\dasm.exe  "-L\IBMinclude\SYS1.MACLIB\&M" 
"-L\IBMinclude\SYS1.MODGEN\&M" "-L\IBMinclude\DSNA10.SDSNMACS\&M" 
"-L\IBMinclude\CEE.SCEEMAC\&M" "-L\IBMinclude\CEE.SCEESAMP\&M" 
"-L\IBMinclude\CICS.SDFHMAC\&M" "-L\IBMinclude\DBCOLE.XDCZ1D.XDCMACS\&M" 
"-L\IBMinclude\DSNA10.SDSNMACS\&M" "-L&p\src\zProtect\asm\&M.mac" 
"-L&p\src\ra\&M.mac" "-LC:\SVN\zFPE6\\asmmacs\&M.mac" 
"-LC:\Progra~2\Dignus\maclib\&M" -quiet -flisting=testCCompiler.zLST 
-idr="5694A01   1900" -o CMakeFiles/cmTryCompileExec.dir/testCCompiler.c.o 
testCCompiler.zASM

But since I’m issuing the build command from the directory above CMakeFiles, I 
can’t tell whether this means that CMake must be copying the file, but I expect 
it is. So how is it managing to copy it but lock it?!
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to