| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: small proposal: pg_config record flag variables? |
| Date: | 2005-08-09 19:21:39 |
| Message-ID: | 42F90243.507@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Currently, pg_config will tell about the configure options that were
>used, but it does not let you find out if any environment variables were
>used to determine CC, CFLAGS, etc. More than once I've found myself
>wanting to verify that information about an installation. So I'm
>considering adding options to pg_config to record the more interesting
>Makefile variables:
>
> pg_config --cc
> pg_config --cppflags
> pg_config --cflags
> pg_config --cflags_sl
> pg_config --ldflags
> pg_config --ldflags_sl
> pg_config --libs
>
>Comments? Are these option names okay, or do they need to be more
>verbose? Any other settings worth recording?
>
>
>
>
I would be tempted to have one flag called, say, --build-env which has
all the interesting settings from the build environment in one hit.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-09 19:25:16 | Re: small proposal: pg_config record flag variables? |
| Previous Message | Andrew - Supernews | 2005-08-09 19:21:33 | Re: Simplifying wal_sync_method |