pgsql-server/src/bin/initdb Makefile
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl@svr1.postgresql.org 03/11/13 16:30:37
Modified files:
src/bin/initdb : Makefile
Log message:
Silly to copy sprompt.c from src/port when we're linking libpgport anyway.
Tom Lane wrote:
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl@svr1.postgresql.org 03/11/13 16:30:37Modified files:
src/bin/initdb : MakefileLog message:
Silly to copy sprompt.c from src/port when we're linking libpgport anyway.
The style has always been to compile in each app in case the flags
change, or is that only for libpq?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Bruce Momjian wrote:
Tom Lane wrote:
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl@svr1.postgresql.org 03/11/13 16:30:37Modified files:
src/bin/initdb : MakefileLog message:
Silly to copy sprompt.c from src/port when we're linking libpgport anyway.The style has always been to compile in each app in case the flags
change, or is that only for libpq?
Never mind --- I see we are not using pgport consistently now and not
using symlinks.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Bruce Momjian <pgman@candle.pha.pa.us> writes:
Silly to copy sprompt.c from src/port when we're linking libpgport anyway.
The style has always been to compile in each app in case the flags
change, or is that only for libpq?
libpq needs to build these modules PIC, but a simple executable does
not. The whole notion of building libpgport as a library is wrong
if you want to recompile in each app.
regards, tom lane