Date: Thu, 26 Jan 1995 17:24:11 +0059 (MET) From: Andreas Schulz <ats@g386bsd.first.gmd.de> To: steve@khoros.unm.edu (Steven Jorgensen) Cc: questions@FreeBSD.org Subject: Re: possible fopen/fclose bug? Message-ID: <199501261624.RAA15626@g386bsd.first.gmd.de> In-Reply-To: <9501260535.AA25049@zen.khoros.unm.edu> from "Steven Jorgensen" at Jan 25, 95 10:35:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> Since this ftruncate is not necessary on the other architectures > we support, I was wondering if this is a bug in freebsd's fclose, > or whether or not it is an undefined action that we've just been > lucky with before this.. :^) Check the imake sources for lseek's and ftruncate's. Many older sources expect that the offset is a long. But FreeBSD has now, like the other 4.4BSD derived Systems a long long instead ( 64 bits vs. 32 bits ). So the lseek and ftruncate should use an "off_t" type, also the intermediate variables where a return from lseek is stored need to be "off_t". ATS ( ats@first.gmd.de or ats@cs.tu-berlin.de ) Andreas Schulz GMD-FIRST 12489 Berlin-Adlershof Rudower Chaussee 5 Gebaeude 13.7 Tel: +49-30-6392-1856/+49-177-2134745 Germany/Europe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199501261624.RAA15626>