On Fri, 20 Apr 2007 15:55:34 -0500,
ArarghMail704NOSPAM@[EMAIL PROTECTED]
wrote:
>>>I have 7 versions of that C compiler, and they all have CL.EXE. Might
>>>help if you mention the version number.
>>Mine is version 7.
>>>Might try cleaning out the "c:\temp" & "c:\windows\temp" directories
>>>and see what happens.
>>I emptied both and nothing changed. The error is still present.
>The only other thing I can think of is that CL.EXE might be trying to
>use either the current directory, or some directory associated with
>the input or output. In any case, whatever directory it is, it needs
>to be writable (or not readonly).
But what directory could that be?
C:\C700 is not readonly, nor are any of its subdirectories.
The working directory is separate and not readonly.
What are the required environmental variables?
>Ver 7 seems to be a bit of an oddity. :-) Run strings on cl.exe (in
>ascii mode).
I do not understand.
>I tend to use vers 6, 8, & 12 when I actually need a C compiler.
Someday I will get the latest version of CL.EXE from MS - it's free.
But for now C700 works for me - almost.
--
"Prediction is very difficult, especially about the future."
--Niels Bohr
|
