Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ames!sgi!davea@quasar.wpd.sgi.com
From: davea@quasar.wpd.sgi.com (David B.Anderson)
Newsgroups: comp.sys.sgi
Subject: Re: 3.3 fortran problem
Summary: setenv TMPDIR /usr/tmp
Message-ID: <70111@sgi.sgi.com>
Date: 24 Sep 90 22:59:26 GMT
References: <9009220353.AA08099@akiko.Princeton.EDU>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 41

In article <9009220353.AA08099@akiko.Princeton.EDU>, phil@AKIKO.PRINCETON.EDU ("Philip D. Jeffrey") writes:
> In article <25656.26f4d43b@kuhub.cc.ukans.edu> arritt@kuhub.cc.ukans.edu writes:
> Status: R
> 
> >Has anyone been having problems compiling Fortran code under 3.3?  I just
> >installed 3.3 and tried to compile one of the models I've been using, and
> >got the following error message:
> >
> >
> >	f77 -static -Olimit 1400 -O1  -c hill2dc.f
> >
> >ugen: internal: error in write, writing 6528 bytes instead of 8192 bytes
> >*** Error code 1
> >
> >Stop.
> >
> >
> 
> It happened to us when compiling a graphics program that compiled fine under
> 3.2 (4D/25TG) and didn't under 3.3 (4D/340VGX). It turned out that /tmp was
> filling up with temporary files written by ugen, if I recall correctly. We
> expanded /tmp using a link to /usr/tmp (the perils of doing this sort of thing
> have been previously discussed on this network), and now the programs compile
> just fine.

A simpler and safer solution  to running out of space during compiles is

	setenv TMPDIR /usr/tmp

(using csh  terminology) for example

or
	TMPDIR=/usr/tmp ; export TMPDIR

(using sh/ksh)

See the f77(1) or cc(1) man page.

Regards,
[ David B. Anderson  Silicon Graphics  (415)335-1548  davea@sgi.com ]
[``What can go wrong?''                          --Calvin and Hobbes]