Skip site navigation (1) Skip section navigation (2)

Re: Building psql.exe using the free Borland compiler

From: ljb <ljb220(at)mindspring(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Building psql.exe using the free Borland compiler
Date: 2006-05-31 01:19:04
Message-ID: e5iqu7$29cu$1@news.hub.org (view raw or flat)
Thread:
Lists: pgsql-interfaces
alvherre(at)commandprompt(dot)com wrote:
>...
> but ISTM ljb is the one who needs to find what works ...

Here's my Makefile for testing this:
===========================
all: f1 f2 f3 f4 f5 f6
f1:
	echo \#define SYSCONFDIR "" > f1
f2:
	echo \#define SYSCONFDIR \"\" > f2
f3:
	echo "#define SYSCONFDIR \"\"" > f3
f4:
	echo '\#define SYSCONFDIR ""' > f4
f5:
	echo '#define SYSCONFDIR ""' > f5
f6:
	echo #define SYSCONFDIR "" > f6
===========================
I'm using make from "Borland C++ 5.5.1 for Win32" on Windows 2000.
Here are the results for the first 4 cases:
f1: #define SYSCONFDIR "" 
f2: #define SYSCONFDIR \"\" 
f3: "#define SYSCONFDIR \"\"" 
f4: '#define SYSCONFDIR ""' 

Cases 'f5' and 'f6' don't produce output files at all.

So it seems to me that the patch to bcc32.mak should be reverted (as shown
below), but that depends on what the original poster (Mark Morgan Lloyd)
says. If he says the patch is needed, we should figure out why we get
different results.

--- src/interfaces/libpq/bcc32.mak.orig	2006-04-24 00:03:42.000000000 -0400
+++ src/interfaces/libpq/bcc32.mak	2006-05-30 19:40:31.000000000 -0400
@@ -141,7 +141,7 @@
 
 # Have to use \# so # isn't treated as a comment, but MSVC doesn't like this
 pg_config_paths.h: bcc32.mak
-	echo \#define SYSCONFDIR \"\" > pg_config_paths.h
+	echo \#define SYSCONFDIR "" > pg_config_paths.h
 
 "$(OUTDIR)" :
 	@if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

In response to

Responses

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2006-05-31 09:16:58
Subject: Re: Building psql.exe using the free Borland compiler
Previous:From: Tom LaneDate: 2006-05-30 23:02:11
Subject: Re: Reset expired password from .NET

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group