| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Giles Lean" <giles(at)nemeton(dot)com(dot)au> |
| Subject: | Re: pg_dump and large files - is this a problem? |
| Date: | 2002-10-29 13:17:25 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961ED6@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > The problem with flex is, that the generated c file does #include <unistd.h>
> > before we #include "postgres.h".
> > In this situation _LARGE_FILES is not defined for unistd.h and unistd.h
> > chooses to define _LARGE_FILE_API, those two are not compatible.
>
> Yeah. AFAICS the only way around this is to avoid doing any I/O
> operations in the flex-generated files. Fortunately, that's not much
> of a restriction.
Unfortunately I do not think that is sufficient, since the problem is already
at the #include level. The compiler barfs on the second #include <unistd.h>
from postgres.h
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tara Piorkowski | 2002-10-29 13:22:21 | Re: Request for supported platforms |
| Previous Message | Pedro Miguel Frazao Fernandes Ferreira | 2002-10-29 11:39:18 | Re: float output precision questions |