aboutsummaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-08-16 02:53:37 +0000
committerUlrich Drepper <drepper@redhat.com>1999-08-16 02:53:37 +0000
commit02228370832f0f150d2be4b7548e5ce97ddae88c (patch)
tree31d28ece5d5b95b7a736ac27e343d32aeaeffffb /INSTALL
parentc9eaa8b9ba58a4c6fb78a62a68068ac5bb51fd3d (diff)
downloadglibc-02228370832f0f150d2be4b7548e5ce97ddae88c.tar
glibc-02228370832f0f150d2be4b7548e5ce97ddae88c.tar.gz
glibc-02228370832f0f150d2be4b7548e5ce97ddae88c.tar.bz2
glibc-02228370832f0f150d2be4b7548e5ce97ddae88c.zip
Update.
1999-07-20 Geoff Keating <geoffk@cygnus.com> * math/libm-test.c: Tweak deltas for a clean run on ppc.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL10
1 files changed, 6 insertions, 4 deletions
diff --git a/INSTALL b/INSTALL
index 9aac7d16a2..6b2928bc99 100644
--- a/INSTALL
+++ b/INSTALL
@@ -32,10 +32,12 @@ below.
Configuring and compiling GNU Libc
==================================
- GNU Libc can be compiled in the source directory but we'd advise to
-build in a separate build directory. For example, if you have unpacked
-the glibc sources in `/src/gnu/glibc-2.1.0', create a directory
-`/src/gnu/glibc-build' to put the object files in.
+ GNU Libc can be compiled in the source directory but we strongly
+advise to build in a separate build directory. For example, if you
+have unpacked the glibc sources in `/src/gnu/glibc-2.1.0', create a
+directory `/src/gnu/glibc-build' to put the object files in. This
+allows to remove the whole build directory in case an error occurs
+which is the safest way to get a clean way and should always be done.
From your object directory, run the shell script `configure' found
at the top level of the source tree. In the scenario above, you'd type