Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Dienstag, 9. August 2005 20:49 schrieb Tom Lane:
>> 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.
> If you put
Am Dienstag, 9. August 2005 20:49 schrieb Tom Lane:
> 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.
If you put these flags onto the configure command line, then th
On Wed, 2005-08-10 at 11:26 -0400, Andrew Dunstan wrote:
> Tom Lane wrote:
> >Simon Riggs <[EMAIL PROTECTED]> writes:
> >
> >>On a related topic, why is pg_config not part of the RPM builds?
> >
> >Hmm? It's definitely in Red Hat's RPMs, can't speak for anyone else's.
> >
> >(Red Hat puts it in
Tom Lane wrote:
Simon Riggs <[EMAIL PROTECTED]> writes:
On a related topic, why is pg_config not part of the RPM builds?
Hmm? It's definitely in Red Hat's RPMs, can't speak for anyone else's.
(Red Hat puts it in the postgresql-devel RPM, which might be a poor
choice, but it's ther
Simon Riggs <[EMAIL PROTECTED]> writes:
> On a related topic, why is pg_config not part of the RPM builds?
Hmm? It's definitely in Red Hat's RPMs, can't speak for anyone else's.
(Red Hat puts it in the postgresql-devel RPM, which might be a poor
choice, but it's there.)
On Tue, 2005-08-09 at 14:49 -0400, 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 inform
On Tue, Aug 09, 2005 at 04:10:08PM -0400, Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > --all would be fine. In fact, why not make it the default?
>
> We could do that. Any objections out there?
+1 in favor of making '--all' the default behavior :)
Cheers,
D
--
David Fetter
I wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> 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.
> The one-flag way would be human readable but not program friendly.
OTOH there's nothing saying
On Tue, Aug 09, 2005 at 03:25:16PM -0400, Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> pg_config --cc
> >> pg_config --cppflags
> >> pg_config --cflags
> >> pg_config --cflags_sl
> >> pg_config --ldflags
> >> pg_config --ldflags_sl
> >> pg_config --libs
>
>
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> --all would be fine. In fact, why not make it the default?
We could do that. Any objections out there?
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postm
Tom Lane wrote:
I wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
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.
The one-flag way would be human readable but not program friendl
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> pg_config --cc
>> pg_config --cppflags
>> pg_config --cflags
>> pg_config --cflags_sl
>> pg_config --ldflags
>> pg_config --ldflags_sl
>> pg_config --libs
> I would be tempted to have one flag called, say, --build-env which has
> all
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
c
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 opt
14 matches
Mail list logo
