Re: Link requirements creep

Поиск
Список
Период
Сортировка
От Marko Kreen
Тема Re: Link requirements creep
Дата
Msg-id e51f66da0805171504w128594bw88ba54eb5955754a@mail.gmail.com
обсуждение исходный текст
Ответ на Link requirements creep  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Link requirements creep  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 5/18/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I was displeased to discover just now that in a standard RPM build of
>  PG 8.3, psql and the other basic client programs pull in libxml2 and
>  libxslt; this creates a package dependency that should not be there
>  by any stretch of the imagination.

>  Thoughts, better ideas?

1. Use  -Wl,--as-needed as linker flag.  Portability unknown...  Can be autoconfed.

2. Lets have few top-level library dependencies as make variables:
  LIBPQ_LDFLAGS (LIBPQ_LIBS?)  LIBPQ_CFLAGS
  Same for READLINE, LIBXML2, etc
  Maybe also BACKEND_*

Then each component can pick groups as it needs.

Basically the default autoconf style of putting all into LIBS
work well only when you have single program to build.  As in
Postgres build-tree we have lots of modules that want different
selection of libraries to link to, this style does not fit.

-- 
marko


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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: use of pager on Windows psql
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: use of pager on Windows psql