diff options
| author | Guido van Rossum <guido@python.org> | 1997-12-30 04:32:30 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 1997-12-30 04:32:30 (GMT) |
| commit | 24df68493a690a2153dd79430ff9800505d81917 (patch) | |
| tree | 47a2dfe9ae84a723c4c3a45c3666ce12fa91e3b7 /README | |
| parent | 14777f87d8c0260435839a63c4f682b2f819c62a (diff) | |
| download | cpython-24df68493a690a2153dd79430ff9800505d81917.zip cpython-24df68493a690a2153dd79430ff9800505d81917.tar.gz cpython-24df68493a690a2153dd79430ff9800505d81917.tar.bz2 | |
Refine note about strftime test failure (it's fixed in Linux glibc 6).
Diffstat (limited to 'README')
| -rw-r--r-- | README | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -473,9 +473,10 @@ produces some output. You can generally ignore the messages about skipped tests due to an optional feature that can't be imported (if you want to test those modules, edit Modules/Setup to configure them). If a messages is printed about a failed test or a traceback or core -dump is produced, something's wrong. On some systems, test_strftime -fails due to a non-standard implementation of strftime() in the C -library. This can be ignored (or you can complain to your vendor). +dump is produced, something's wrong. On some Linux systems (those +that are not yet using glibc 6), test_strftime fails due to a +non-standard-compliant implementation of strftime() in the C library. +Please ignore this, or upgrade to glibc version 6. IMPORTANT: If the tests fail and you decide to mail a bug report, *don't* include the output of "make test". It is useless. Run the |