Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:10926 comp.os.386bsd.apps:1323 comp.os.386bsd.questions:12035
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!cs.utexas.edu!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!scsing.switch.ch!news.dfn.de!urmel.informatik.rwth-aachen.de!news.rhrz.uni-bonn.de!saph2.physik.uni-bonn.de!juengst
From: juengst@saph2.physik.uni-bonn.de (Henry G. Juengst)
Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.apps,comp.os.386bsd.questions
Subject: Re: __NetBSD__ X11R6 i386
Date: 3 Aug 1994 10:08:13 GMT
Organization: Physikalisches Institut der Universitaet Bonn
Lines: 60
Distribution: world
Message-ID: <31nqad$mii@news.rhrz.uni-bonn.de>
References: <30dr4j$phk@darum.uni-mannheim.de> <bakulCtsIBF.4BH@netcom.com> <31mgdu$s9d@news.rhrz.uni-bonn.de> <deeken.775902001@iti.informatik.th-darmstadt.de>
Reply-To: juengst@saph2.physik.uni-bonn.de
NNTP-Posting-Host: saph2.physik.uni-bonn.de
In article <deeken.775902001@iti.informatik.th-darmstadt.de>, deeken@iti.informatik.th-darmstadt.de (Hannes Deeken) writes:
>juengst@saph2.physik.uni-bonn.de (Henry G. Juengst) writes:
>
>>>this you need to either have a proper lseek() declaration in
>>>imake.c's scope, or a quick and dirty fix is to just use a
>
>>"A proper lseek() declaration in imake.c's scope" ? What did you study ?
>>Dentistry ? :-)
>
>>Lseek is a function of your OS. So, please add the required #include
>>statements, use what your OS declares and use a C compiler which handles
>>prototypes. Do not use an old cc.
>
>HUH? That's exactly what he's saying!
>The "proper lseek() declaration" is found in unistd.h, and it is brought
>into imake.c's scope by adding an #include directive a la '#include <unistd.h>
>to the source.
To say 'bring it into imake's scope' and to say 'use the include file
of the OS' is not the same. The first one could also mean, that one uses
his/her/its private - proper - declaration. That's what happens in many
applications. It is not ok to declare a foreign identifer in your own
source file. The only compatible way is to include the required header
files of the foreign software.
Anyway, the imake specific problem is in the ftruncate function call,
but the previous statement is also true for this one.
>BTW: 386BSD, FreeBSD and NetBSD all use gcc, so there's no need to bitch
>about compilers which don't grok prototypes.
>
>>Declarations of OS specific identifiers have nothing to do in applications.
>
>No? Applications don't use facilities provided by the OS? Interresting view...
I didn't write "facilities", I wrote "declarations".
I'm pissed off by all those sys_errlist, lseek etc. declarations in too
many programs. I know that there are some poor systems without complete
OS specific header files, but for those chests one could declare the
missing identifiers between #ifdef osname ... #endif.
>
>
>Hannes
Henry
>--
>Hans-Christoph Deeken | hannes@flinx.{RoBIN.de,hotb.sub.org} (home)
>Paul-Wagner-Str. 58 | deeken@iti.informatik.th-darmstadt.de (university)
>64285 Darmstadt | IRC: Glenlivet
>
--
juengst@saph2.physik.uni-bonn.de [131.220.221.12] (internet)
juengst@boss1.physik.uni-bonn.de [131.220.221.30]
saph2::juengst [13.259] (decnet)
Any opinions in this mail are my own.