Re: build environment: a different makefile - Mailing list pgsql-hackers

From Tom Lane
Subject Re: build environment: a different makefile
Date
Msg-id 19718.1202339551@sss.pgh.pa.us
Whole thread Raw
In response to Re: build environment: a different makefile  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: build environment: a different makefile  ("Dave Page" <dpage@postgresql.org>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I don't know if anyone has a makefile for it, but the following seems to work
> for me:

> pgsql/src/backend$ cc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement
-Wendif-labels-fno-strict-aliasing -g -L../../src/port  -Wl,-rpath,'/home/peter/devel/pg83/pg-install/lib' -Wl,-E
$(find-name "*.o" | grep -v SUBSYS | grep -v conversion_procs) ../../src/timezone/SUBSYS.o
../../src/port/libpgport_srv.a-lxslt -lxml2 -lpam -lssl -lcrypto -lgssapi_krb5 -lcrypt -ldl -lm -lldap -o postgres
 

> If you find that the optimizations you are hoping for are useful, I'm sure
> we could put an option of that sort somewhere in the makefiles.

I've sometimes wondered whether the SUBSYS.o files really offer any
advantage compared to just linking all the individual .o files.  They
certainly eat disk space, but perhaps they save some time ... or perhaps
not, especially in a one-off build.

I suppose that we might fall foul of command line length limits on
some platforms :-(.  The output of your find command amounts to nearly
11000 characters in HEAD.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: PostgreSQL 8.4 development plan
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL 8.4 development plan