It wasn't properly fixed in the upstream.
PR: 248973
Submitted by: Andrey Pevnev <apevnev@me.com> (maintainer)
Reported by: Jose Luis Duran <jlduran@gmail.com>
Event: September 2020 Bugathon
Also, add patch to support colorized output for `keactl status`.
PR: 241349
Submitted by: Jose Luis Duran <jlduran@gmail.com>
Approved by: Andrey Pevnev <apevnev@me.com> (maintainer)
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
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 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, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
Leap-second smearing is an experimental option that may be specified in
ntp.conf(5) to spread the effect of a leap-second over an interval as
specified by the leapsmearinterval config file statement. Recommended
values are between 7200 (2 hours) and 86400 (24 hours).
It is advised that leap-second smearing not be used for public NTP
servers (https://www.meinbergglobal.com/download/burnicki/Leap\
%20Second%20Smearing%20With%20NTP.pdf). It is also advised that NTP
clients not use a mix of NTP servers using leap-second smearing with
NTP servers not using leap-second smearing as that could cause
undefined client behaviour.
Suggested by: des
`_ZZN5boost6system15system_categoryEvE21system_category_const' referenced in section `.text' of .libs/libkea_asiolink_la-io_address.o: defined in discarded section `.bss._ZZN5boost6system15system_categoryEvE21system_category_const[_ZZN5boost6system15system_categoryEvE21system_category_const]' of .libs/libkea_asiolink_la-io_address.o
`_ZZN5boost6system16generic_categoryEvE22generic_category_const' referenced in section `.text' of .libs/libkea_asiolink_la-io_address.o: defined in discarded section `.bss._ZZN5boost6system16generic_categoryEvE22generic_category_const[_ZZN5boost6system16generic_categoryEvE22generic_category_const]' of .libs/libkea_asiolink_la-io_address.o
[...]
PR: 199601
Reported by: antoine (via exp-run)
Approved by: portmgr blanket
hide actual commands executed and only show short summary line (like
"CC foo.c"). CMake and ninja enable this by default, some autotools
using ports do as well. This is unacceptable because we need complete
build logs at any time, so we now switch to verbose build logs
unconditionally. Note that this change deliberately affects ALL
builds and not only package builds on cluster, because we need to
be sure that user experiencing failure can always provide informative
build log regardless of settings and without rerunning the build.
Change summary:
- Always do verbose builds for cmake, ninja and GNU configure (the
latter includes check if --disable-silent-rules is actually supported
by the configure script; there are isolated cases when it's not true)
- Remove CMAKE_VERBOSE, NINJA_VERBOSE and
CONFIGURE_ARGS=--disable-silent-rules from all ports which set them
for this is no longer needed
- Revert hacks for --disable-silent-rules support priorly committed
to biology/ncbi-blast+ and net-p2p/mldonkey - no longer needed as well
Submitted by: amdmi3
Reviewed by: mat
Exp-run by: antoine
Approved by: portmgr (mat, antoine)
Differential Revision: D7534
Alexey Dokuchaev
Kurt Jaeger
Danilo G. Baio
Li-Wen Hsu
Jan Beich
Jochen Neumeister
Tobias Kortkamp
Koichiro Iwao
Baptiste Daroussin
Piotr Kubaj
Gerald Pfeifer
Hiroki Sato
Dmitry Marakasov
Mark Linimon
Cy Schubert
Mathieu Arnold