You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tom Lane e9a3c047a5 Always use -fPIC, not -fpic, when building shared libraries with gcc. ... On some platforms, -fpic fails for sufficiently large shared libraries. We've mostly not hit that boundary yet, but there are some extensions such as Citus and pglogical where it's becoming a problem. A bit of research suggests that the penalty for -fPIC is small, in the single-digit-percentage range --- and there's none at all on popular platforms such as x86_64. So let's just default to -fPIC everywhere and provide one less thing for extension developers to worry about. Per complaint from Christoph Berg. Back-patch to all supported branches. (I did not bother to touch the recently-removed Makefiles for sco and unixware in the back branches, though. We'd have no way to test that it doesn't break anything on those platforms.) Discussion: https://postgr.es/m/20170529155850.qojdfrwkkqnjb3ap@msg.df7cb.de		9 years ago
..
Makefile	…
Makefile.aix	…
Makefile.cygwin	Try to fix non-MSVC Windows builds in the wake of logical replication.	9 years ago
Makefile.darwin	…
Makefile.freebsd	…
Makefile.hpux	…
Makefile.linux	Always use -fPIC, not -fpic, when building shared libraries with gcc.	9 years ago
Makefile.netbsd	Always use -fPIC, not -fpic, when building shared libraries with gcc.	9 years ago
Makefile.openbsd	Always use -fPIC, not -fpic, when building shared libraries with gcc.	9 years ago
Makefile.solaris	…
Makefile.win32	Try to fix non-MSVC Windows builds in the wake of logical replication.	9 years ago
pgxs.mk	…