Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Or should FRONTEND perhaps even be explicitly #defined in postgres_fe.h?
> You know, that is an excellent idea. I have been adding FRONTEND to
> specific Makefiles just in cases where I need special src/port compiles
> of files, but putting it in postgr
Magnus Hagander wrote:
> Hi!
>
> Is there any reason why FRONTEND is not specified in the ecpg build
> (specifically the pgtypeslib)? I'm running into build problems because
> it pulls backend-specific stuff from port.h in
> (postgres_fe.h->c.h->port.h) when tweaking the timezone code.
>
> Or sho
Magnus Hagander wrote:
> Hi!
>
> Is there any reason why FRONTEND is not specified in the ecpg build
> (specifically the pgtypeslib)? I'm running into build problems because
> it pulls backend-specific stuff from port.h in
> (postgres_fe.h->c.h->port.h) when tweaking the timezone code.
>
> Or sho
Hi!
Is there any reason why FRONTEND is not specified in the ecpg build
(specifically the pgtypeslib)? I'm running into build problems because
it pulls backend-specific stuff from port.h in
(postgres_fe.h->c.h->port.h) when tweaking the timezone code.
Or should FRONTEND perhaps even be explicitly
