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

Re: Capturing binary and other output destined for "make install"

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Doug Knight <dknight(at)wsi(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Capturing binary and other output destined for "make install"
Date: 2007-06-27 20:20:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Doug Knight wrote:
>   Is there a way within the existing installation mechanisms to capture 
> the files generated by an execution of "make", compiling from source, 
> that are copied to their locations during the "make install"? For 
> example, I had considered executing a "make -n install", capturing that 
> output, and turning it into a script. I'm not looking to make an RPM. 
> I've been tasked to automate our build/install process so that we build 
> once (including packages related to postgres like PostGIS, and some of 
> our own applications), and install from the result of the build onto a 
> number of internal servers.

make install;
make -C contrib install
tar -czvf pgsql.tar.gz /usr/local/pgsql


Joshua D. Drake

> Thanks,
> Doug Knight


       === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997

Donate to the PostgreSQL Project:
PostgreSQL Replication:

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-06-27 20:21:37
Subject: Re: AutoVacuum Behaviour Question
Previous:From: Heikki LinnakangasDate: 2007-06-27 20:17:21
Subject: Re: todo: Hash index creation

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