On Fri, 12 May 2000, Koster, K.J. wrote:
> Unless this has been changed from 3.4 to 4.0, gcc defaults to /var/tmp. I
> never understood why, and the gcc manual page claims that it's /tmp (I
> think). MFS users, synchronize your TMPDIR variables ... now. :-)
It did.
Compiling a simple test program just now shows:
+ -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccl22910.i
+ -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccc22910.s
+ -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccP22910.o
- -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccl22910.i
- -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccc22910.s
- -rw------- 1 root wheel 0 May 12 00:16 /tmp/ccP22910.o
(incidentally, another reason to use -pipe is that the above filenames are
predictable and probably handled insecurely so that another user can cause
any of your files to be overwritten when you compile something. This is
on my list of things to fix).
Kris
----
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
