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

31 lines
867 B
Makefile
Raw Normal View History

Update memtester to 4.2.1 Changelog: Version 4.2.1 3 October 2010 -fix offsets/addresses were not being reported correctly in test failure messages. Thanks: Anton Sergeev. Version 4.2.0 30 July 2010 -define _FILE_OFFSET_BITS to 64 by default in conf-cc, which causes some 32-bit systems with larger-than-32-bit address spaces to have a 64-bit off_t, allowing testing of larger chunks of memory. Thanks to Steven A. Falco for the suggestion. Let me know if this definition causes problems for anyone. -add tests of 8-bit-wide and 16-bit-wide random writes, to enable verifying the correct operation of hardware. Thanks: Dick Hollenbeck. If these tests trigger unaligned access problems on your platform, you can eliminate these tests by removing the -DTEST_NARROW_WRITES definition from the conf-cc file.
2010-10-26 22:22:04 +02:00
# $NetBSD: Makefile,v 1.20 2010/10/26 20:22:04 zafer Exp $
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
#
Update memtester to 4.2.1 Changelog: Version 4.2.1 3 October 2010 -fix offsets/addresses were not being reported correctly in test failure messages. Thanks: Anton Sergeev. Version 4.2.0 30 July 2010 -define _FILE_OFFSET_BITS to 64 by default in conf-cc, which causes some 32-bit systems with larger-than-32-bit address spaces to have a 64-bit off_t, allowing testing of larger chunks of memory. Thanks to Steven A. Falco for the suggestion. Let me know if this definition causes problems for anyone. -add tests of 8-bit-wide and 16-bit-wide random writes, to enable verifying the correct operation of hardware. Thanks: Dick Hollenbeck. If these tests trigger unaligned access problems on your platform, you can eliminate these tests by removing the -DTEST_NARROW_WRITES definition from the conf-cc file.
2010-10-26 22:22:04 +02:00
DISTNAME= memtester-4.2.1
Cosmetic increase in whitespace (no functional change).
2004-08-10 07:20:54 +02:00
CATEGORIES= sysutils
Update to 4.0.6. From the changelog: - test algorithm improvement: the walking 0 bits test was only walking the 0 bit in one direction, instead of walking it up and back down the line the way it was intended to. Thanks: Tim Rule. - formatting cleanups.
2007-01-11 05:02:53 +01:00
MASTER_SITES= ${HOMEPAGE}old-versions/
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
Take MAINTAINER at author's long-ago request. No response from previous maintainer within two weeks.
2005-02-04 02:00:23 +01:00
MAINTAINER= schmonz@NetBSD.org
HOMEPAGE moved. Take MAINTAINER for queue_repair at author's months-ago request.
2005-02-16 19:44:36 +01:00
HOMEPAGE= http://pyropus.ca/software/memtester/
Cosmetic increase in whitespace (no functional change).
2004-08-10 07:20:54 +02:00
COMMENT= Utility for testing the memory subsystem for faults
Update to 4.1.2. From the changelog: - fix portability issue with MAP_LOCKED flag. Thanks: Scott Haneda. - remove debugging output accidentally left in v.4.1.0. - cleanups - memtester.h was missing from the 4.1.0 tarball; release update to fix that. Thanks: Owen Leonard. - added the ability to test a specific physical region of memory (by mmap'ing /dev/mem) with the new -p option, which takes a hex starting address as a value. This is mostly of use to developers trying to verify memory or I/O mapped devices (on an embedded system, for instance). Thanks: Allon Stern. - re-add the ability to set a suffix on the memory to allocate: "3G", "128K", etc, mostly for use with the above new feature, where the "memory" to be tested is less than a megabyte, but also useful for users wanting to test many gigabytes; you no longer have to do the conversion-to-megs in your head. - documentation updates and clarifications.
2009-08-03 17:51:40 +02:00
LICENSE= gnu-gpl-v2
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
NOT_FOR_PLATFORM Interix, as it has no m[un]lock(2).
2005-11-01 20:01:17 +01:00
NOT_FOR_PLATFORM= Interix-*-* # no m[un]lock(2), so not useful anyway
Update to 4.1.2. From the changelog: - fix portability issue with MAP_LOCKED flag. Thanks: Scott Haneda. - remove debugging output accidentally left in v.4.1.0. - cleanups - memtester.h was missing from the 4.1.0 tarball; release update to fix that. Thanks: Owen Leonard. - added the ability to test a specific physical region of memory (by mmap'ing /dev/mem) with the new -p option, which takes a hex starting address as a value. This is mostly of use to developers trying to verify memory or I/O mapped devices (on an embedded system, for instance). Thanks: Allon Stern. - re-add the ability to set a suffix on the memory to allocate: "3G", "128K", etc, mostly for use with the above new feature, where the "memory" to be tested is less than a megabyte, but also useful for users wanting to test many gigabytes; you no longer have to do the conversion-to-megs in your head. - documentation updates and clarifications.
2009-08-03 17:51:40 +02:00
PKG_DESTDIR_SUPPORT= user-destdir
Enable pkgviews installation.
2004-07-28 18:03:47 +02:00
PKG_INSTALLATION_TYPES= overwrite pkgviews
Convert to use djbware.mk.
2005-08-07 13:47:55 +02:00
DJB_RESTRICTED= NO
Introduce DJB_MAKE_TARGETS boolean, on by default, off in the following packages because they don't use "it" and "setup check" as BUILD_TARGET and INSTALL_TARGET, respectively: devel/bglibs mail/mailfront mail/qmail-qfilter sysutils/memtester sysutils/qlogtools Since there's only one consumer of BGWARE_INSTALLER, and future bgware will use bg-installer from bglibs, move the do-install routine directly into qlogtools.
2005-08-24 06:47:10 +02:00
DJB_MAKE_TARGETS= NO
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
Mechanically replaced man/* with ${PKGMANDIR}/* in the definition of INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with ${PREFIX}/${PKGMANDIR}. Fixes PR 35265, although I did not use the patch provided therein.
2007-01-07 10:13:46 +01:00
INSTALLATION_DIRS= bin ${PKGMANDIR}/man8 share/doc/memtester
Update to 4.0.5. From the changelog: -change to the method of allocating and locking memory; if we get EPERM when trying to mlock(), reset the amount of memory desired to the original amount and try again without mlock(). The reason for this is that on many systems, mlock() won't return EPERM until after having returned ENOMEM for a larger amount. The new behaviour allows processes without mlock privileges to still test the fully-specified amount or as much memory as can be allocated. Thanks for the suggestion and testing to Dan Bradley.
2005-03-22 01:07:36 +01:00
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
do-install:
Update to 4.1.2. From the changelog: - fix portability issue with MAP_LOCKED flag. Thanks: Scott Haneda. - remove debugging output accidentally left in v.4.1.0. - cleanups - memtester.h was missing from the 4.1.0 tarball; release update to fix that. Thanks: Owen Leonard. - added the ability to test a specific physical region of memory (by mmap'ing /dev/mem) with the new -p option, which takes a hex starting address as a value. This is mostly of use to developers trying to verify memory or I/O mapped devices (on an embedded system, for instance). Thanks: Allon Stern. - re-add the ability to set a suffix on the memory to allocate: "3G", "128K", etc, mostly for use with the above new feature, where the "memory" to be tested is less than a megabyte, but also useful for users wanting to test many gigabytes; you no longer have to do the conversion-to-megs in your head. - documentation updates and clarifications.
2009-08-03 17:51:40 +02:00
cd ${WRKSRC} && \
${INSTALL_PROGRAM} memtester ${DESTDIR}${PREFIX}/bin; \
${INSTALL_MAN} memtester.8 ${DESTDIR}${PREFIX}/${PKGMANDIR}/man8; \
${INSTALL_DATA} README.tests ${DESTDIR}${PREFIX}/share/doc/memtester
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
Convert to use djbware.mk.
2005-08-07 13:47:55 +02:00
.include "../../mk/djbware.mk"
Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by <pancake at phreaker.net> with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby <sim@stormix.com>. I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.
2004-07-16 02:49:20 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink