Re: 7.1 beta 3 CHANGES FOR QNX - Mailing list pgsql-hackers

From Maurizio
Subject Re: 7.1 beta 3 CHANGES FOR QNX
Date
Msg-id 003d01c08f58$9498a6a0$7394fea9@maurizio
Whole thread Raw
In response to Re: 7.1 beta 3 CHANGES FOR QNX  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: 7.1 beta 3 CHANGES FOR QNX
List pgsql-hackers
ECHO is defined in the following QNX gcc include files :
termio.h
termios.h

If ECHO was not redefined in pgc.l you can't compile in embedded SQL C.

I am also checking for another problem.
I have some errors if I compile pgsql without change the typedef Size in
c.h.
To succesfully compile pgsql I have changed typedef Size in int insteed
size_t.

regards
Maurizio Cauci



.
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Bruce Momjian" <pgman@candle.pha.pa.us>
Cc: "Maurizio" <maurizio.c@libero.it>; <pgsql-hackers@postgresql.org>
Sent: Saturday, February 03, 2001 9:49 PM
Subject: Re: [HACKERS] 7.1 beta 3 CHANGES FOR QNX


> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > *** src/interfaces/ecpg/preproc/pgc.l 2001/01/24 19:43:29 1.73
> > --- src/interfaces/ecpg/preproc/pgc.l 2001/02/02 18:13:17
> > ***************
> > *** 35,40 ****
> > --- 35,45 ----
> >   #undef yywrap
> >   #endif /* yywrap */
>
> > + #ifdef __QNX__
> > + /* For some reason, QNX needs this, 2001-02-02 */
> > + #define ECHO (void) fwrite( yytext, yyleng, 1, yyout )
> > + #endif
> > +
> >   #define YY_NO_UNPUT
>
> >   extern YYSTYPE yylval;
>
> I do not believe this patch is correct or necessary.  What is it trying
> to fix, and if there's a problem here then why is there not a problem in
> every other one of our flex outputs?
>
> If there is a real problem --- presumably of the form "some QNX header
> file pollutes the namespace with a definition of ECHO" ---  then a more
> appropriate fix would be
>
> + #ifdef __QNX__
> + /* Get rid of conflicting definition of ECHO from QNX's <something.h> */
> + #undef ECHO
> + #endif
>
> so as not to tie ourselves to the exact definition of ECHO that flex is
> currently using.  However, I would first like to know where the conflict
> is and why it doesn't break every other flex output in existence.
>
> regards, tom lane



pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: Re: Re: Format of the Money field
Next
From: "Oliver Elphick"
Date:
Subject: Stuck Spinlock (fwd) - m68k architecture, 7.0.3