FRRouting (FRR) is an IP routing protocol suite for Linux and Unix platforms
which includes protocol daemons for BGP, IS-IS, OSPF and RIP. FRR has its roots
in the Quagga project.
WWW: https://frrouting.org/
===> The following configuration options are available for frr4-4.0.1_1:
FPM=off: Enable Forwarding Plane Manager support
LDPD=off: Build ldpd
MULTIPATH=off: Enable multipath function
PAM=off: Use libpam for PAM support in vtysh
RPKI=on: Add BGP RPKI (RFC 6810) support
SHELLACCESS=off: Allow users to access shell/telnet/ssh
TCMALLOC=off: Use tcmalloc
TCPSOCKETS=off: Use TCP/IP sockets for protocol daemons
VTYSH=on: Build integrated vty shell
===> Use 'make config' to modify these settings
FRR's OSPF daemons tries to allocate big socket buffer, so generate warning
messages like:
"setsockopt_so_sendbuf: fd 6: SO_SNDBUF set to 1048576 (requested 8388608)"
To prevent such message kern.ipc.maxsockbuf can be increased:
sysctl kern.ipc.maxsockbuf=16777216
Error messages like "if_ioctl(SIOCGIFMEDIA) failed: Invalid argument" are
under investigation.
Bump PORTREVISION for ports depending on the canonical version of GCC
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
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
Bump PORTREVISION for ports depending on the canonical version of GCC
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
Adjust USES to fix builds on gcc-based architectures.
While here, pet portlint.
Tested for no regression on amd64.
Approved by: portmgr (tier-2 blanket)
Due to stability problems with FRR 4.0, reintroduce previous FRR 3.0.3.
Merge watchfrr RC script from frr4 that was improved and update frr4's
conflicts port list.
Sponsored by: Orange
Due to regression detected on FRR 4.0, preparing re-introduction of
FRR 3 branch by renaming frr to frr4.
Fixed a typo regarding my last modification into MOVED file too.
