Changeset 503 in kBuild for trunk/src/gmake/tests/README
- Timestamp:
- Sep 15, 2006 5:09:38 AM (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/src/gmake/tests/README
r53 r503 1 This is release 3.78 (September 6, 1999) of the GNU make test 2 suite. See the file NEWS for some of the changes since the last 3 release. 1 The test suite was originally written by Steve McGee and Chris Arthur. 2 It is covered by the GNU General Public License (Version 2), described 3 in the file COPYING. It has been maintained as part of GNU make proper 4 since GNU make 3.78. 4 5 5 This release is made by [email protected] to correspond to GNU make 3.78. 6 It won't work correctly for versions before that. In addition to some 7 infrastructure changes I've added a number of new tests. 6 This entire test suite, including all test files, are copyright and 7 distributed under the following terms: 8 8 9 Rob Tulloh has contributed changes to get the suite running on NT. 9 ----------------------------------------------------------------------------- 10 Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 11 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. 12 This file is part of GNU Make. 10 13 11 Eli Zaretskii and Esa A E Peuha <[email protected]> have contributed 12 changes to get the suite running on DJGPP/DOS. 14 GNU Make is free software; you can redistribute it and/or modify it under the 15 terms of the GNU General Public License as published by the Free Software 16 Foundation; either version 2, or (at your option) any later version. 13 17 14 This package has a number of problems which preclude me from 15 distributing it with make as a default "make check" test suite. The 16 most serious of these is that it's not parallelizable: it scribbles all 17 over its installation directory and so can only test one make at a 18 time. I simply don't have time to do more with this than I am so far; 19 I'm very actively interested in finding someone willing to overhaul the 20 test suite infrastructure. If you're interested, contact me (see below)! 18 GNU Make is distributed in the hope that it will be useful, but WITHOUT ANY 19 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR 20 A PARTICULAR PURPOSE. See the GNU General Public License for more details. 21 21 22 The test suite thus far has been written by Steve McGee, Chris Arthur, 23 and Paul D. Smith. It is covered by the GNU General Public License 24 (Version 2), described in the file COPYING. 22 You should have received a copy of the GNU General Public License along with 23 GNU Make; see the file COPYING. If not, write to the Free Software 24 Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 25 ----------------------------------------------------------------------------- 25 26 26 The test suite requires Perl and is known to work with Perl 4.036 and 27 Perl 5.004 (available from ftp.gnu.org, and portable to many machines). 28 Earlier or later versions may work; I don't know. It assumes that the 29 first "diff" it finds is GNU diff, but that only matters if a test 30 fails. 27 The test suite requires Perl. These days, you should have at least Perl 28 5.004 (available from ftp.gnu.org, and portable to many machines). It 29 used to work with Perl 4.036 but official support for Perl 4.x was 30 abandoned a long time ago, due to lack of testbeds, as well as interest. 31 32 The test suite assumes that the first "diff" it finds on your PATH is 33 GNU diff, but that only matters if a test fails. 31 34 32 35 To run the test suite on a UNIX system, use "perl ./run_make_tests" … … 44 47 45 48 Tests cannot end with a "~" character, as the test suite will ignore any 46 that do (I was tired of having it run my Emacs backup files as test :) 47 48 If you want to run the tests in parallel, you should use the mkshadow 49 script included here to create temporary "copies" (via symbolic links) 50 of the test suite, one for each parallel job. This is a pain and one 51 day maybe the test suite will be rewritten so it's no longer 52 necessary--volunteers welcome! 49 that do (I was tired of having it run my Emacs backup files as tests :)) 53 50 54 51 Also, sometimes the tests may behave strangely on networked 55 52 filesystems. You can use mkshadow to create a copy of the test suite in 56 53 /tmp or similar, and try again. If the error disappears, it's an issue 57 with your network or file server, not GNU make (I believe). 54 with your network or file server, not GNU make (I believe). This 55 shouldn't happen very often anymore: I've done a lot of work on the 56 tests to reduce the impacts of this situation. 58 57 59 58 The options/dash-l test will not really test anything if the copy of … … 73 72 other possible options for the test suite. 74 73 74 75 Open Issues 76 ----------- 77 78 The test suite has a number of problems which should be addressed. One 79 VERY serious one is that there is no real documentation. You just have 80 to see the existing tests. Use the newer tests: many of the tests 81 haven't been updated to use the latest/greatest test methods. See the 82 ChangeLog in the tests directory for pointers. 83 84 The second serious problem is that it's not parallelizable: it scribbles 85 all over its installation directory and so can only test one make at a 86 time. The third serious problem is that it's not relocatable: the only 87 way it works when you build out of the source tree is to create 88 symlinks, which doesn't work on every system and is bogus to boot. The 89 fourth serious problem is that it doesn't create its own sandbox when 90 running tests, so that if a test forgets to clean up after itself that 91 can impact future tests. 92 93 94 Bugs 95 ---- 96 75 97 Any complaints/suggestions/bugs/etc. for the test suite itself (as 76 opposed to problems in make that the suite finds) should be sent to 77 [email protected]. Enjoy! 98 opposed to problems in make that the suite finds) should be handled the 99 same way as normal GNU make bugs/problems (see the README for GNU make). 100 101 78 102 Paul D. Smith 79 103 Chris Arthur
Note:
See TracChangeset
for help on using the changeset viewer.