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
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)
PGroonga is a PostgreSQL extension. PGroonga provides a new index access
method that uses Groonga.
Groonga is an embeddable super fast full text search engine. It can be
embedded into MySQL. Mroonga is a storage engine that is based on Groonga.
Groonga can also work as standalone search engine.
PostgreSQL supports full text search against languages that use only
alphabet and digit. It means that PostgreSQL doesn't support full text
search against Japanese, Chinese and so on. You can use super fast full
text search feature against all languages by installing PGroonga into your
PostgreSQL!
WWW: https://pgroonga.github.io/
