The attached patch against PostgreSQL-8.2.1 was discussed on [INTERFACES].
It fixes bcc32.mak makefiles for the Borland BCC compiler to build libpq
and psql*. There are also changes to some header files to hide some things
BCC doesn't like.

*Note: psql compiles with bcc after the patch, but it does not run very well.


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

On Tue, 9 Jan 2007, L Bayuk wrote:

> The attached patch against PostgreSQL-8.2.1 was discussed on [INTERFACES].
> It fixes bcc32.mak makefiles for the Borland BCC compiler to build libpq
> and psql*. There are also changes to some header files to hide some things
> BCC doesn't like.
>
> *Note: psql compiles with bcc after the patch, but it does not run very well.
>

Define "does not run very well" :-)

Gavin

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Gavin Sherry wrote:
> On Tue, 9 Jan 2007, L Bayuk wrote:
>
> > The attached patch against PostgreSQL-8.2.1 was discussed on [INTERFACES].
> > It fixes bcc32.mak makefiles for the Borland BCC compiler to build libpq
> > and psql*. There are also changes to some header files to hide some things
> > BCC doesn't like.
> >
> > *Note: psql compiles with bcc after the patch, but it does not run very well.
> >
>
> Define "does not run very well" :-)

See:

http://archives.postgresql.org/pgsql...1/msg00003.php

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Tue, 9 Jan 2007, Bruce Momjian wrote:

> Gavin Sherry wrote:
> > On Tue, 9 Jan 2007, L Bayuk wrote:
> >
> > > The attached patch against PostgreSQL-8.2.1 was discussed on [INTERFACES].
> > > It fixes bcc32.mak makefiles for the Borland BCC compiler to build libpq
> > > and psql*. There are also changes to some header files to hide some things
> > > BCC doesn't like.
> > >
> > > *Note: psql compiles with bcc after the patch, but it does not run very well.
> > >
> >
> > Define "does not run very well" :-)
>
> See:
>
> http://archives.postgresql.org/pgsql...1/msg00003.php
>

*blinks*

Can we be sure that a BCC build libpq is even safe to use given the
problems seen when using psql?

Gavin

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Gavin Sherry wrote:
> On Tue, 9 Jan 2007, Bruce Momjian wrote:
>
> > Gavin Sherry wrote:
> > > On Tue, 9 Jan 2007, L Bayuk wrote:
> > >
> > > > The attached patch against PostgreSQL-8.2.1 was discussed on [INTERFACES].
> > > > It fixes bcc32.mak makefiles for the Borland BCC compiler to build libpq
> > > > and psql*. There are also changes to some header files to hide some things
> > > > BCC doesn't like.
> > > >
> > > > *Note: psql compiles with bcc after the patch, but it does not run very well.
> > > >
> > >
> > > Define "does not run very well" :-)
> >
> > See:
> >
> > http://archives.postgresql.org/pgsql...1/msg00003.php
> >
>
> *blinks*
>
> Can we be sure that a BCC build libpq is even safe to use given the
> problems seen when using psql?

The bcc users say it is.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Gavin Sherry <swm@linuxworld.com.au> writes:
> Can we be sure that a BCC build libpq is even safe to use given the
> problems seen when using psql?

Well, I'd not trust it a lot, but surely we have to get it to build
before anyone can debug it ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Tom Lane wrote:
> Gavin Sherry <swm@linuxworld.com.au> writes:
> > Can we be sure that a BCC build libpq is even safe to use given the
> > problems seen when using psql?
>
> Well, I'd not trust it a lot, but surely we have to get it to build
> before anyone can debug it ...

It does build, but the report is that psql crashes after a few commands.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Bruce Momjian wrote:
> Tom Lane wrote:
> > Gavin Sherry <swm@linuxworld.com.au> writes:
> > > Can we be sure that a BCC build libpq is even safe to use given the
> > > problems seen when using psql?
> >
> > Well, I'd not trust it a lot, but surely we have to get it to build
> > before anyone can debug it ...
>
> It does build, but the report is that psql crashes after a few commands.

What about a Mingw or VC++ psql with a BCC libpq? Is it possible to
link something like that?

It would be nice to have the libpq at least able to pass the regression
tests.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Gavin Sherry <swm@linuxworld.com.au> writes:
> > > > Can we be sure that a BCC build libpq is even safe to use given the
> > > > problems seen when using psql?
> > >
> > > Well, I'd not trust it a lot, but surely we have to get it to build
> > > before anyone can debug it ...
> >
> > It does build, but the report is that psql crashes after a few commands.
>
> What about a Mingw or VC++ psql with a BCC libpq? Is it possible to
> link something like that?

No idea.

> It would be nice to have the libpq at least able to pass the regression
> tests.

True.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

On 1/10/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:

> What about a Mingw or VC++ psql with a BCC libpq? Is it possible to
> link something like that?
>
> It would be nice to have the libpq at least able to pass the regression
> tests.

you can use microsoft/mingw compiled DLL files but not library files.
however, borland provides a command line tool (implib i thnk) to
create an import library for it which works ok. (i think you have to
pass a switch to fix underscore issue).

libpq.lib is not directly usable (coff vs. omf) but digital mars makes
a tool which can do this and I have confirmed it works.

note: I've used borland compiled libpq (not psql) with borland C++
builder 3 & 5 with no problems. I had to hack pg_config.h however.

merlin

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq