Re: build environment: a different makefile

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Paul van den Bogaard <Paul(dot)Vandenbogaard(at)sun(dot)com>
Subject: Re: build environment: a different makefile
Date: 2008-02-06 23:12:31
Message-ID: 19718.1202339551@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-02-06 23:50:34 Re: PostgreSQL 8.4 development plan
Previous Message Greg Smith 2008-02-06 23:01:49 Re: PostgreSQL 8.4 development plan