Personally, i dislike environment variable dependence. Maybe that's exposure to lexical binding poisoning my tastes... In any case, (info "(autoconf) Defining Variables") has more info.
thi _________________________________________________________________________ >From 7a7b846cc2eb1f6aadfb06ccb445642f2bc2dfa7 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen <[email protected]> Date: Sat, 9 Jan 2010 10:07:48 +0100 Subject: [PATCH] Update configure script hints wrt precious env vars. * README: Don't suggest setting vars before running configure. Instead, suggest specifying them on the configure command-line. Signed-off-by: Thien-Thi Nguyen <[email protected]> --- README | 19 +++++++++++-------- 1 files changed, 11 insertions(+), 8 deletions(-) diff --git a/README b/README index 5669ce8..e799495 100644 --- a/README +++ b/README @@ -50,16 +50,19 @@ names (where that is supported), makes it impossible to later move the built executables and libraries to an installation location other than the one that was specified at build time. -Another possible approach is to set CPPFLAGS and LDFLAGS before -running configure, so that they include -I options for all the +Another possible approach is to set CPPFLAGS and LDFLAGS on the +configure command-line, so that they include -I options for all the non-standard places where you have installed header files and -L options for all the non-standard places where you have installed libraries. This will allow configure and make to find those headers -and libraries during the build. The locations found will not be -hardcoded into the build executables and libraries, so with this -approach you will probably also need to set LD_LIBRARY_PATH -correspondingly, to allow Guile to find the necessary libraries again -at runtime. +and libraries during the build. E.g.: + + ../configure [...] CPPFLAGS='-I/my/include' LDFLAGS='-L/my/lib' + +The locations found will not be hardcoded into the build executables and +libraries, so with this approach you will probably also need to set +LD_LIBRARY_PATH correspondingly, to allow Guile to find the necessary +libraries again at runtime. Required External Packages ================================================ @@ -94,7 +97,7 @@ Guile requires the following external packages: compile and link options for libgc. If you don't have pkg-config installed, or you have a version of libgc that doesn't provide a .pc file, you can work around this by setting some environment - variables before running ./configure: + as part of the configure command-line: - PKG_CONFIG=true -- 1.6.3.2
