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
- Improve warning when third party "-4/-6" is not supported
- Add af=inet/inet6 to verbose UDP output
- Add ip=<server_ip> to verbose UDP output for client transmitter
- Fix to pass "-4" or "-6" argument to 3rd party
- Fix to allow compile with -Werror=format-security as noted by
Dhiru Kholia in fedora bug 1037224
- Fix missing brackets caught by -Wmisleading-indentation
- Add code to print out address family of connect/accept
- Add code to translate v4mapped addresses
- Fix to allow direct I/O on block devices
- Fix parsing of "-R i[s]##[/##]" (blank between 'R' and 'i')
- Updated Copyright notice for new year
- Changed nuttcp site to http://nuttcp.net/nuttcp/beta/
- Added define test for NOT_LINUX to undefine LINUX for build testing
- Add reporting of TCP congestion window
- Fix tos to work for ipv6 by setting traffic class
PR: 232484
Submitted by: lev
took a look into upstream's Gopkg.lock, checking for modifications;
changed 2 depencies to use version instead of revision;
google:go-cmp and golang:text
get QA done right; thanks to portlint;
moved PLIST_FILES to appear after USES.
Approved by: araujo (mentor), rene (mentor)
Differential Revision: https://reviews.freebsd.org/D17530
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
This module attempts to implement reasonably robust benchmarking with little
extra effort and expertise required from the user. That is to say, benchmarking
using this module is likely an improvement over
time some-command --to --benchmark
or
use Benchmark qw/timethis/;
timethis(1000, 'system("some-command", ...)');
The module currently works similar to the former command line, except (in layman
terms) it will run the command many times, estimate the uncertainty of the
result and keep iterating until a certain user-defined precision has been
reached. Then, it calculates the resulting uncertainty and goes through some
pain to discard bad runs and subtract overhead from the timings. The reported
timing includes an uncertainty, so that multiple benchmarks can more easily be
compared.
Please note that Dumbbench works entirely with wallclock time as reported by
Time::HiRes' time() function.
WWW: https://metacpan.org/release/Dumbbench
While I'm upgrading, I fix the atomic 64 bit detection on clang6
The current solution is to for the noinline attribute to the
atomic detection code
PR: 229885
Based on the timeout of 3+ months (2018-03-23-now) on bug#226885 for net/ucarp
Also, looking at the subversion log, there were timeouts on:
* bug#224169 r465659 | ygy | 2018-03-26 19:51:12
* bug#224768 r459066 | swills | 2018-01-15 07:16:28
* bug#224755 r459058 | swills | 2018-01-15 06:55:08
The last approval from alexey@renatasystems.org was over a year ago:
bug#218563 r438885 | lifanov | 2017-04-19 08:30:28 (devel/py-colorama)
