as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
postgresql, <arpa/inet.h> was included automatically as part of the
postgres module building environment. But it needs to be included
explicitly for the most recent postgres.
Submitted by: andriy@irbisnet.com
Just updating PORTVERSION won't achieve anything if you don't also
make the corresponding change to GH_TAGNAME. To avoid this sort of
embarrassment in future, drop PORTVERSION and GH_TAGNAME for the main
distfile in favour of DISTVERSION and DISTVERSIONPREFIX.
Reorder some items in the Makefile to mollify portlint.
Reported by: mat
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
cc: error: invalid linker name in argument '-fuse-ld=bfd'
Neither emaste nor I can figure out exactly where the offending stanza is
coming in. It will take someone with more knowledge of gmake debug flags,
and possibly the src build infrastructure, to figure it out.
While here, pet portlint.
Approved by: portmgr (tier-2 blanket)
Switch to downloading sources from GitHub, and add the pglogical_dump
submodule. This was omitted from the tarball provided by 2nd Quadrant
in the latest version. The pglogical_dump code is only compiled with
postgresql9.4 which failed to build -- using other postgresql versions
worked fine.
Reported by: pkg-fallout
pglogical-output: delete; merged into databases/pglogical
The databases/pglogical and databases/pglogical-output ports have been
merged into one codebase upstream, and database/pglogical now installs
the pglogical-output.so module.
pkg(8) should handle the merger correctly; portmaster(1),
portupgrade(1) users are advised to manually delete pglogical-output
before upgrading.
release tarball, but has been fixed in upstream's Github.
Add pglogical_dump, pglogical_origin--1.0.0.sql and
pglogical_origin.control conditionally on the postgresql version --
these are only compiled and installed with postgresql-9.4.x
Submitted by: Anderson Neves <anderson.ufal@gmail.com>
PostgreSQL extension. Fully integrated, it requires no triggers or
external programs. This alternative to physical replication is a
highly efficient method of replicating data using a publish/subscribe
model for selective replication.
WWW: http://2ndquadrant.com/en/resources/pglogical/
