The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
This uses sched_getcpu(2) to find the CPU we are scheduled on and then
cpufreq(4) to find the frequency of that CPU. The caller is responsible
for pinning the thread to one CPU and/or disabling frequency scaling if
a consistent result is required.
Maintainer requests to be relieved of maintainership of some of his
ports due to lack of time.
Approved by: Clockwork6400@protonmail.com (maintainer, via IRC)
I forgot to include this patch originally. While the warning is
harmless (sigjmp_buf and jmp_buf have the same layout on FreeBSD),
it might not be on downstream ports consumers like DragonflyBSD.
libcpucycles is a microlibrary for counting CPU cycles. Cycle counts
are not as detailed as Falk diagrams but are the most precise timers
available to typical software; they are central tools used in
understanding and improving software performance.
The libcpucycles API is simple: include <cpucycles.h>, call cpucycles()
to receive a long long whenever desired, and link with -lcpucycles.
Internally, libcpucycles understands machine-level cycle counters for
amd64 (both PMC and TSC), arm32, arm64 (both PMC and VCT), mips64,
ppc32, ppc64, riscv32, riscv64, s390x, sparc64, and x86. libcpucycles
also understands four OS-level mechanisms, which give varying levels of
accuracy: mach_absolute_time, perf_event, CLOCK_MONOTONIC, and, as a
fallback, microsecond-resolution gettimeofday.
When the program first calls cpucycles(), libcpucycles automatically
benchmarks the available mechanisms and selects the mechanism that does
the best job. Subsequent cpucycles() calls are thread-safe and very
fast. An accompanying cpucycles-info program prints a summary of
cycle-counter accuracy.
WWW: https://cpucycles.cr.yp.to/
Tested by: jhibbits
- Fix version requirement of RUN_DEPENDS
- Bump PORTREVISION for dependency change
from gitlab-derailed_benchmarks.gemspec:
s.add_runtime_dependency(%q<get_process_mem>.freeze, ["~> 0".freeze])
Note that this port still does not pass stage-qa.
====> Running Q/A tests (stage-qa)
Error: RubyGem dependency memory_profiler ~> 0 is not satisfied.
*** Error code 1
This port can be removed since it is not used by any port.
- Fix version requirement of RUN_DEPENDS
- Bump PORTREVISION for dependency change
from derailed_benchmarks.gemspec [1]:
gem.add_dependency "get_process_mem", "~> 0"
Note that this port still does not pass stage-qa.
====> Running Q/A tests (stage-qa)
Error: RubyGem dependency memory_profiler ~> 0 is not satisfied.
*** Error code 1
This port can be removed since it is not used by any port.
Reference: https://github.com/zombocom/derailed_benchmarks/blob/v1.7.0/derailed_benchmarks.gemspec#L27 [1]
- Update MASTER_SITES: use upstream release tarball
- Use USES=pathfix to fix .pc installation
- Bump PORTREVISION of dependent ports for shlib change
Changes: https://github.com/google/googletest/releases
- Use GitHub is primary site for MASTER_SITES and es.net as fallback
- Use variables in MASTER_SITES
- Minor adjustments to Makefile
Changelog: https://github.com/esnet/iperf/releases/tag/3.17.1
PR: 278918
Reviewed by: bmah (maintainer)
Franco Fichtner
Gabriel M. Dutra
Yuri Victorovich
Muhammad Moinur Rahman
Jan Beich
Robert Clausecker
Bruce A. Mah
Mikael Urankar
Rene Ladan
Po-Chuan Hsieh
Dima Panov
Matthias Fechner
Kirill Ponomarev
Luca Pizzamiglio
Siva Mahadevan
Ashish SHUKLA
Alexey Dokuchaev
Stephen Montgomery-Smith
Vsevolod Stakhov
Daniel Engberg