Increase array test sizes and reps to wash out sampling error on modern
hardware, where run times were becoming too short and inconsistent.
A few other minor enhancements
Update the CONFLICTS definitions of ports in the following categories:
- accessibility
- archivers
- audio
- benchmarks
- biology
- cad
- chinese
- comms
- converters
An attempt has been made to use generic conflicts patterns that do not
have to be updated whenever a new version of a conflicting port is
added to the ports system.
There is a misunderstanding that the port being built/installed has to
be omitted from the conflicts pattern. This is not true - the port
being built is implicitly non-conflicting due to logic in bsd.port.mk.
Approved by: portmgr (implicit)
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
cannot conflict with itself (due to logic in bsd.port.mk that
supresses the pattern match result in that case).
A few ports that set the conflicts variables depending on complex
conditions (e.g. port options), have been left unmodified, despite
probably containing outdated package names.
These changes should only affect the installation of locally built
ports, not the package building with poudriere. They should give an
early indication of the install conflict in cases where currently
the pkg command aborts an installation when it detects that an
existing file would be overwritten,
Approved by: portmgr (implicit)
The CPU_SET macros in -CURRENT have been made compatible with GLIBC.
A simple test for the new signature of CPU_AND, CPU_OR, ... is the
existence of a CPU_ALLOC macro.
Approved by: portmgr (implicit)
MFH: 2022Q1
In CURRENT, the initial configuration detects now support for the
scheduler affinity, enabling the build of an additional stressor.
In this stressor, the CPU_OR macro has 3 arguments (Linux implementation),
while on FreeBSD it has only 2 arguments.
This patch provides the fix
No bumprevision is provided, because it's only fixing CURRENT where the
build was failing.
- Report CPU frequency and temperature on the HUD
- For gathering system information, use sysctlbyname() if
possible instead of capturing external programs' output
Now comes with CPU load monitoring enabled by default and better
system information report in debug mode. Note that those things
currently require mounted linprocfs(5) to work.
Reported by: portscout
- Add missing dependency for playing music: USE_LINUX+=openal-soft
- In the `do-extract', rather than changing current directory, pass it to
tar(1) as a -C argument and don't needlessly use semi-private _DISTDIR
variable: this makes the command shorter and avoids bogus double slash
in the build log
- Provide more user-friendly wrapper script which anticipates potential
problems that typically affect running this program and advises on how
to solve them
- Spell GNU/Linux correctly in the COMMENT and port description; reformat
the latter with `fmt -w 75' for better looks (less ragged right edge)
error[E0432]: unresolved imports `core::sync::atomic::AtomicI64`, `core::sync::atomic::AtomicU64`
--> /wrkdirs/usr/ports/benchmarks/inferno/work/inferno-0.10.7/cargo-crates/crossbeam-utils-0.8.5/src/lib.rs:79:49
|
79 | pub(crate) use core::sync::atomic::{AtomicI64, AtomicU64};
| ^^^^^^^^^ ^^^^^^^^^ no `AtomicU64` in `sync::atomic`
| |
| no `AtomicI64` in `sync::atomic`
|
help: a similar name exists in the module
|
79 | pub(crate) use core::sync::atomic::{AtomicI8, AtomicU64};
| ~~~~~~~~
help: a similar name exists in the module
|
79 | pub(crate) use core::sync::atomic::{AtomicI64, AtomicU8};
| ~~~~~~~~
error[E0412]: cannot find type `AtomicU64` in module `core::sync::atomic`
--> /wrkdirs/usr/ports/benchmarks/inferno/work/inferno-0.10.7/cargo-crates/crossbeam-utils-0.8.5/src/atomic/consume.rs:78:14
|
78 | impl_atomic!(AtomicU64, u64);
| ^^^^^^^^^ help: a struct with a similar name exists: `AtomicU16`
error[E0412]: cannot find type `AtomicI64` in module `core::sync::atomic`
--> /wrkdirs/usr/ports/benchmarks/inferno/work/inferno-0.10.7/cargo-crates/crossbeam-utils-0.8.5/src/atomic/consume.rs:80:14
|
80 | impl_atomic!(AtomicI64, i64);
| ^^^^^^^^^ help: a struct with a similar name exists: `AtomicI16`
Some errors have detailed explanations: E0412, E0432.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `crossbeam-utils` due to 3 previous errors
Unigine benchmarks are extreme performance and stability test for your
hardware: video card, power supply, cooling system. Check your rig in
stock and overclocked modes with real-life load!
These two benchmarks depict a Gothic chapel and a tropical paradise.
WWW: https://benchmark.unigine.com/
