Please don't flag packages in case of a "compilation error for about two months". The problem was initially only reported by one user so I assumed that it would be a local issue and didn't care too much. Besides the initial comment was not even including the linker invocation itself. How should I investigate a linker error without knowing the linker flags?
My own build conduced in a clean chroot succeeded. I assume you guys all didn't use a clean chroot and are instead building the package while the previous version is still installed on the system. Can you at least try to uninstall the previous version before? Judging by the linker line from @doragasu comment I assume gcc/ld will pick up the installed version rather than the newly built version. That seems to be a limitation of PostgreSQL's build system. It wouldn't be the first package of that kind (e.g. Qt's build system suffers from the same problem).
Pinned Comments
Martchus commented on 2017-06-03 13:19 (UTC) (edited on 2019-01-28 13:06 (UTC) by Martchus)
Important note
This package must be built in a clean chroot or at least without the previous version being installed. Otherwise PostgeSQL's build system seems to pick up the installed version of certain libraries rather than the version produced by the current build. (You would get a linker error like
undefined reference to 'AllocSetContextCreateExtended'
.)All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs There also exist a binary repository: https://martchus.no-ip.biz/repo/arch/ownstuff