summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-05-21 01:31:08 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-05-21 01:31:08 +0000
commit5749690fd49fb1966f7dcf313324348f068fb2a2 (patch)
treee3b3d4fd161133e021f537a0b8c6a31a92490e55 /INSTALL
parent74298e20df82d0caf85a6d961c0c5ef19163cfca (diff)
downloadmpfr-5749690fd49fb1966f7dcf313324348f068fb2a2.tar.gz
To take into account that Automake 1.13 or later will be used:
* doc/mpfr.texi, INSTALL: updates related to "make check". * configure.ac: require Automake 1.13 since the documentation now assumes that 1.13 or later is used (and because previous Automake versions are no longer tested); also added AM_PROG_AR to support unusual archivers (after a warning from Automake 1.13). (merged changesets r8546,8572-8573,8611,9375,9380 from the trunk) git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/branches/3.1@9434 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL11
1 files changed, 10 insertions, 1 deletions
diff --git a/INSTALL b/INSTALL
index c29dbdfd2..442ff3f94 100644
--- a/INSTALL
+++ b/INSTALL
@@ -72,6 +72,14 @@ MPFR).
5. To check the built library (runs the test files), type:
make check
+ Note: If any test fails, information about this failure can be found in
+ the tests/test-suite.log file; you should provide this file in your bug
+ reports (in addition to other useful information, as mentioned later).
+ If you want the contents of this file to be automatically output in case
+ of failure, you can set the VERBOSE environment variable to 1 before
+ running "make check", for instance by typing:
+ VERBOSE=1 make check
+
6. To install it (default "/usr/local" | see "--prefix" option), type:
make install
@@ -438,7 +446,8 @@ mailing-list <mpfr@inria.fr>, indicating the machine and operating system
used (uname -a), the compiler and version used (gcc -v if you use gcc),
the configure options used if any (including variables such as CC and
CFLAGS), the version of GMP and MPFR used, and a description of the
-problem encountered. Please send us also the log of the "configure"
+problem encountered, in particular the tests/test-suite.log file if
+"make check" failed. Please send us also the log of the "configure"
(config.log).
Note that even if you can build MPFR with a C++ compiler, you can't run