RE: [RFC] building postgres with meson - v13

Поиск
Список
Период
Сортировка
От shiy.fnst@fujitsu.com
Тема RE: [RFC] building postgres with meson - v13
Дата
Msg-id OSZPR01MB63109A247B4A7BC92F60D12FFD249@OSZPR01MB6310.jpnprd01.prod.outlook.com
обсуждение исходный текст
Ответ на Re: [RFC] building postgres with meson - v13  (Andres Freund <andres@anarazel.de>)
Ответы Re: [RFC] building postgres with meson - v13  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Fri, Oct 14, 2022 12:40 AM Andres Freund <andres@anarazel.de> wrote:
>
> Hi,
>
> On 2022-10-13 09:24:51 +0000, shiy.fnst@fujitsu.com wrote:
> > I noticed that `pg_config --configure` didn't show the options given when
> > building with meson.
>
> Yes, that was noted somewhere on this thread.
>
>
> > Maybe it would be better if pg_config can output this information, to be
> > consistent with the output when building with `./configure` and `make`.
> >
> > The output when building with `./configure` and `make`:
> > $ pg_config --configure
> >  '--prefix=/home/postgres/install/' '--cache' 'gcc.cache' '--enable-dtrace' '--
> with-icu' '--enable-cassert'
>
> It'd be a fair amount of work, both initially and to maintain it, to generate
> something compatible. I can see some benefit in showing some feature
> influencing output in --configure, but compatible output doesn't seem worth it
> to me.
>

I agree that there are some benefits to showing that, which helps to confirm the
build options. Although that can be confirmed from the compile log, but the log
may not be available all the time.

And it's ok for me that the output is not exactly the same as before.

Regards,
Shi yu



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: GUC values - recommended way to declare the C variables?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [RFC] building postgres with meson - v13