kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/sysutils/memtest86/Makefile

27 lines
749 B
Makefile
Raw Normal View History

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.
2012-02-19 12:14:32 +01:00
# $NetBSD: Makefile,v 1.23 2012/02/19 11:14:32 obache Exp $
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
#
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.
2012-02-19 12:14:32 +01:00
DISTNAME= memtest86-4.0
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
CATEGORIES= sysutils
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.
2012-02-19 12:14:32 +01:00
MASTER_SITES= ${MASTER_SITE_FREEBSD}
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
Reset maintainer, ben@ has resigned.
2006-12-15 15:34:18 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
HOMEPAGE= http://www.memtest86.com/
COMMENT should start with a capital letter.
2003-07-21 19:24:16 +02:00
COMMENT= Thorough, stand alone memory test for x86 arch
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.
2012-02-19 12:14:32 +01:00
LICENSE= gnu-gpl-v2
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
Make memtest86 build on Linux.
2004-04-18 01:26:06 +02:00
ONLY_FOR_PLATFORM= NetBSD-*-i386 Linux-*-i386
This package is i386 only, so mark it as such.
2002-06-08 09:47:09 +02:00
Support staged installation.
2009-12-12 20:34:46 +01:00
PKG_DESTDIR_SUPPORT= user-destdir
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions: USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-05-22 22:07:36 +02:00
USE_TOOLS+= gmake
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
do-install:
Support staged installation.
2009-12-12 20:34:46 +01:00
${INSTALL_DATA_DIR} ${DESTDIR}${PREFIX}/mdec
${INSTALL_DATA} ${WRKSRC}/memtest ${DESTDIR}${PREFIX}/mdec
${INSTALL_DATA} ${WRKSRC}/memtest.bin ${DESTDIR}${PREFIX}/mdec
${INSTALL_DATA_DIR} ${DESTDIR}${PREFIX}/share/doc/memtest
${INSTALL_DATA} ${WRKSRC}/README ${DESTDIR}${PREFIX}/share/doc/memtest
Re-import memtest as memtest86 (more similar to its original name, and who knows, a memtest package might come soon ;).
2002-03-07 15:44:36 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink