From 30d624f6d99b2fdeaa467ae2242d11f82dfbeff4 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Wed, 18 Apr 2007 04:02:05 +0000 Subject: [PATCH] Mention CPP. --- INSTALL | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/INSTALL b/INSTALL index 9d0376965a4..ce4359f86da 100644 --- a/INSTALL +++ b/INSTALL @@ -364,11 +364,12 @@ Some tests might fail because the compiler should look in special directories for some header files, or link against optional libraries, or use special compilation options. You can force `configure' and the build process which follows it to do that by -setting the variables CPPFLAGS, CFLAGS, LDFLAGS, LIBS, and CC before -running `configure'. CPPFLAGS lists the options passed to the -preprocessor, CFLAGS are compilation options, LDFLAGS are options used -when linking, LIBS are libraries to link against, and CC is the -command which invokes the compiler. +setting the variables CPPFLGS, CFLAGS, LDFLAGS, LIBS, CPP and CC before +running `configure'. CPP is the command which invokes the +preprocessor, CPPFLAGS lists the options passed to it, CFLAGS are +compilation options, LDFLAGS are options used when linking, LIBS are +libraries to link against, and CC is the command which invokes the +compiler. Here's an example of a `configure' invocation, assuming a Bourne-like shell such as Bash, which uses these variables: -- 2.39.2