Re: pgsql: Build src/port files as a library with -fPIC, and use thatin li
От | Andrew Dunstan |
---|---|
Тема | Re: pgsql: Build src/port files as a library with -fPIC, and use thatin li |
Дата | |
Msg-id | 11d432a5-659e-81da-3722-513d039515e1@2ndQuadrant.com обсуждение исходный текст |
Ответ на | pgsql: Build src/port files as a library with -fPIC,and use that in li (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pgsql: Build src/port files as a library with -fPIC, and use that in li
|
Список | pgsql-committers |
On 09/27/2018 11:23 AM, Tom Lane wrote: > Build src/port files as a library with -fPIC, and use that in libpq. > > libpq and ecpg need shared-library-friendly versions of assorted src/port/ > and src/common/ modules. Up to now, they got those by symlinking the > individual source files and compiling them locally. That's baroque, and a > pain to maintain, and it results in some amount of duplicated compile work. > It might've made sense when only a couple of files were needed, but the > list has grown and grown and grown :-( > > It makes more sense to have the originating directory build a third variant > of libpgport.a/libpgcommon.a containing modules built with $(CFLAGS_SL), > and just link that into the shared library. Unused files won't get linked, > so the end result should be the same. > > This patch makes a down payment on that idea by having src/port/ build > such a library and making libpq use it. If the buildfarm doesn't expose > fatal problems with the approach, I'll extend it to the other cases. > Looks like we have a bunch of failures, including prairiedog. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-committers по дате отправления: