From:	kuku AT acds DOT physik DOT rwth-aachen DOT de (Christoph Kukulies)
Subject:	Re: _opoen and open, _close and close, quid ?
To:	TAUPIN AT rsovax DOT lps DOT u-psud DOT fr
Date:	Sat, 24 Sep 1994 18:04:35 +0200 (MET DST)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu (user alias)

> 
> Subject: gcc compiling of f2c output
> 
> 
> I'm trying to gcc-compile and link a file produced by f2c (Fortran to C)
> comiler. The output file (huge) is compiled OK on HP_UX. But when I attempt
> to gcc-compile it, I get undevined symbols "_open" "_close" (possibly others).
> After searching the C files, I find in a f2c libry include file, namely
> RAWIO.H, the following sequence:
> 
> #ifdef MSDOS
> #include "io.h"
> #define close _close
> #define creat _creat
> #define open _open
> #define read _read
> #define write _write
> #endif
> 
> Question: if I cancel these definitions (since "open" is known), will I be
> OK ?
> 

If it is obvious that you are defining MSDOS for some reason - You
should not define MSDOS when compiling DJGPP programs- then it's o.k.
if you remove the #define's.

But first find out why you need to have to define MSDOS.


.
> Daniel Taupin
> 
> 

--Chris  Christoph P. U. Kukulies    kuku AT acds DOT physik DOT rwth-aachen DOT de	 
FreeBSD 1.1.5(RELEASE) (GILMULTICAST) #0: Mon Aug 15 13:10:28 MET DST 1994

- Raw text -