It is more consistent with the tex.buildlink3.mk name. Also, if a package
really needs latex, it just has to set TEX_ACCEPTED to latex distributions
altough today, all TEX_ACCEPTED possibilities are latex distributions
fix the signal handling to use a volatile variable. Compilers can
optimise the access otherwise. Bump revision, since this is a bugfix.
Reviewed by jlam and the maintainer.
directories to process. The removal of pre-configure fixes the config.*
handling at the same time. Also specify the config.status overrides.
Patch configure to not try to detect -lrfftw, just link the static
version explicitly. Do the same for -lfftw. This ensures that we
actually do get the static versions without having to worry about
libtool being too clever. Retire manual config.sub hacks, this should be
handled by config.guess already.
<jlam> just go ahead and commit that benchfft patch and let's
<jlam> never speak of it again :)
While there, use fsync(2) on all hosts. Without this, the fstime benchmark
will be disproportionately biased toward OS's and hardware that buffer
larger amounts of data in memory before [background] syncing.
Classic Unix fork() bomber. Includes CPU hanger, memory allocator,
memory toucher and zombie dance team. You can test how will your
computer behave under heavy CPU, process, memory load.
Forkbomb is also useful as realloc() benchmark.
This benchmark utility is used to determine how the processor,
its caches and coprocessors influence overall system performance.
Its measurements can indicate problems with the processor subsystem
and (since the processor is a major influence on overall system
system performance) give us an idea of how well a given system will
perform.
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
This package is from rpaulo@, who asked me to import.
(My only change was to use INSTALLATION_DIRS.)
I only tested build.
DESCR:
thrulay is used to measure the capacity of a network by sending a bulk
TCP stream over it.
Like other tools (such as iperf, netperf, nettest, nuttcp, ttcp, etc.),
thrulay can report TCP throughput periodically so that TCP performance
plots can be produced. Unlike other tools, thrulay not only reports goodput,
but round-trip delay time as well. The output of thrulay is easy to parse
by machine (in fact, it's ready to be used as a data file for gnuplot).
Starting from version 0.5, thrulay supports UDP tests. Unique feature of
thrulay is that it can send a Poisson stream of very precisely positioned
packets; the TSC register is used for timing rather than very coarse
(20ms on most systems) system sleep functionality.
