Log message:
memtest86: Remove as abandoned (no longer having a Free upstream)

For a really long time, memtestplus has been the successor, and there
has been no discussion of this for years.

Deletion proposed long ago, I'm pretty sure.

Log message:
memtest86: don't use ssp/fortify, like memtestplus.

No idea if this works, it doesn't build on netbsd.

Log message:
Follow some redirects.

Log message:
Add SHA512 digests for distfiles for sysutils category

Problems found with existing digests:
	Package memconf distfile memconf-2.16/memconf.gz
	b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
	95748686a5ad8144232f4d4abc9bf052721a196f [calculated]

Problems found locating distfiles:
	Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
	Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
	Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
	Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
	Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Log message:
Note that this program is no longer maintained upstream as Free
software and point to memtestplus.

Note the presence of 4.0s on the FreeBSD distfiles site.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Update memtest86 to 4.0.
Based on PR 45754 by Radoslaw Kujawa.

Enhancements in v4.0 (28/Mar/2011)
* Support for testing with multiple CPUs. All tests except for #11 (Bit Fade)
  have been multi-threaded. A maximum of 16 CPUs will be used for testing.
* CPU detection has been completely re-written to use the brand ID string rather
  than the cumbersome, difficult to maintain and often out of date CPUID family
  information. All new processors will now be correctly identified without
  requiring code support.
* All code related to controller identification, PCI and DMI has been removed.
  This may be a controversial decision and was not made lightly. The following
  are justifications for the decision:
    1. Controller identification has nothing to do with actual testing of memory,
     the core purpose of Memtest86.
    2. This code needed to be updated with every new chipset. With the ever
       growing number of chipsets it is not possible to keep up with the changes.
       The result is that new chipsets were more often than not reported
       in-correctly. In the authors opinion incorrect information is worse
       than no information.
    3. Probing for chipset information carries the risk of making the program
       crash.
    4. The amount of code involved with controller identification was quite
       large, making support more difficult.

  Removing this code also had the unfortunate effect of removing reporting of
  correctable ECC errors. The code to support ECC was hopelessly intertwined the
  controller identification code. A fresh, streamlined implementation of ECC
  reporting is planned for a future release.
* A surprising number of conditions existed that potentially cause problems when
  testing more than 4 GB of memory. Most if not all of these conditions have
  been identified and corrected.
* A number of cases were corrected where not all of memory was being tested. For
  most tests the last word of each test block was not tested. In addition an
  error in the paging code was fixed that omitted from testing the last 256
  bytes of each block above 2 GB.
* The information display has been simplified and a number of details that were
  not relevant to testing were removed.
* Memory speed measurement has been parallelized for more accurate reporting for
  multi channel memory controllers.
* This is a major re-write of the Memtest86 with a large number of minor
  bug-fixes and substantial cleanup and re-organization of the code.

Log message:
Support staged installation.