to optimize away the loop used for timing. Do something in the loop for
arm that can't be optimized away, and will also meet the 1,000
instructions in the loop requirement.
This allows mhz to calculate sensible Mhz on a StrongArm (228Mhz rather
than 56Mhz)
Other hardware probably also need fixing, as gcc probably applies the same
optimizations on them.
Also bump PKGREVISION.
needed for troubleshooting). And use BINOWN and BINGRP because user "bin"
and group "bin" don't exist on some systems.
Use BSD_INSTALL_PROGRAM, BSD_INSTALL_DATA and BSD_INSTALL_SCRIPT
instead of calling /usr/bin/install directly.
Okayed by maintainer.
Bumped PKGREVISION, since ownership of files may be different on
some systems.
PLIST.${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST.${OPSYS}-${MACHINE_ARCH:C/i[3-6]86/i386/g}
and remove the package hack for MD PLIST files.
While here merge the PLIST.md file into PLIST.common and put the
@dirrm commands into the new PLIST.common_end
(using DIST_SUBDIR).
Diff is:
diff -r old/hbench-OS/README new/hbench-OS/README
12a13,14
> If you would like to share your results, please mail
> them to hbench-results@eecs.harvard.edu.
51a54,56
> If you would like to share your results, please mail
> them to hbench-results@eecs.harvard.edu.
>
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
doesn't enable any functionality. It is here as a marker, so people building
binary packages know that these packages have version-specific features
that would make them incompatible with other point releases.. (such as
LKM's)
