Re: Building psql.exe using the free Borland compiler

Bruce (et al.), sorry- I've only just spotted the activity. I've only got the
one version of the compiler, and since apart from Delphi I have very little
Windows development stuff set up (in particular I am not a C/C++ programmer, and
I'm trying to avoid Cygwin since it can mess up Lazarus) I've got limited scope
for tinkering.

I'll try and test the revised version as soon as I am able and will obviously
report back if there are problems- together with any fixes if I'm able to work
out what's going wrong.

I'd add here that I am indebted to a couple of more experienced C men on CIX for
a hint that enabled me to hack the _pclose problem, although there may be issues
relating to other versions of the compiler- that's one reason why I modified the
source rather than trying to fix things in the makefile.

Keep up the good work and hopefully I've been able to make some tiny
contribution :-)

Bruce Momjian wrote:
>
> With no report back from markMLl, I have changed the BCC code to use ""
> rather than \"\". Backpatched to 8.1.X.
>
> ---------------------------------------------------------------------------
>
> ljb wrote:
> > pgman(at)candle(dot)pha(dot)pa(dot)us wrote:
> > >...
> > > As far as echo, I think you are right that the Win32 command processor
> > > is the one handling that, but I assumed the backslashes were handled by
> > > the Makefile, hence the need for \#.
> >
> > Sort of. It looks to me like \# is handled by make when reading the
> > Makefile, resulting in a # which is not the start of a Makefile comment.
> > But it also seems that \ followed by anything else is not handled specially,
> > but simply passed through to the command.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]