Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12525 comp.os.386bsd.misc:3309 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!netnews.nwnet.net!selway.umt.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: Disk activity when compiling (was Re: Whats wrong with Linux networking ??? ) Date: 19 Aug 1994 15:00:01 GMT Organization: Montana State University, Bozeman Montana Lines: 26 Message-ID: <332hdh$7ki@pdq.coe.montana.edu> References: <1994Aug15.034939.20997@cs.brown.edu> <32te9lINN6ab@bonnie.sax.de> <3306b9$502@nntp2.stanford.edu> NNTP-Posting-Host: 153.90.192.29 In article <3306b9$502@nntp2.stanford.edu>, Dan Yergeau <yergeau@leland.Stanford.EDU> wrote: >|> Are you sure your temp files go via the ramdisk? > >If I'm not mistaken, on FreeBSD, cc's temp files go to either >/usr/tmp or /var/tmp, not /tmp. You should 'setenv TMPDIR /tmp' to >get them to go to the MFS/ramdisk partition. Right, if you look at the gcc sources, it sets the temp files to TMPDIR, which is set to /var/tmp in the include files. TMPDIR was *supposed* to be for temporary files that should be kept over a reboot (ala. editor save files), but gcc uses it to determine where any temp files can exist. This could be changed in GCC to go to /tmp, but no-one has made it a priority to change the current behavior. Fixing it permanently is a trivial fix, and should be made to the file /usr/src/gnu/cc/cc/cc.c. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | home #: (406) 586-0579 | Available for contract/otherwise work.