From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: bug-guile@gnu.org
Subject: Re: [PATCH] Update configure script hints wrt precious env vars.
Date: Wed, 13 Jan 2010 09:19:08 +0100 [thread overview]
Message-ID: <871vhuwh6r.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3wrznm82c.fsf@pobox.com> (Andy Wingo's message of "Tue, 12 Jan 2010 20:34:03 +0100")
From eb2713038b601abd59fdf377847510f27fd17e83 Mon Sep 17 00:00:00 2001
From: Thien-Thi Nguyen <ttn@gnuvola.org>
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 <ttn@gnuvola.org>
---
BTW, apparently, this is the space for comments;
"git am" should ignore all this stuff.
thi
README | 21 ++++++++++++---------
1 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/README b/README
index 5669ce8..ea68081 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 ================================================
@@ -93,8 +96,8 @@ Guile requires the following external packages:
Guile's ./configure script uses pkg-config to discover the correct
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:
+ .pc file, you can work around this by setting some variables as
+ part of the configure command-line:
- PKG_CONFIG=true
--
1.6.3.2
next prev parent reply other threads:[~2010-01-13 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 13:49 [PATCH] Update configure script hints wrt precious env vars Thien-Thi Nguyen
2010-01-09 22:31 ` Andy Wingo
2010-01-10 17:37 ` Thien-Thi Nguyen
2010-01-12 19:34 ` Andy Wingo
2010-01-13 8:19 ` Thien-Thi Nguyen [this message]
2010-01-13 19:52 ` Andy Wingo
2010-01-13 20:35 ` Thien-Thi Nguyen
2010-01-13 21:06 ` Andy Wingo
2010-01-14 11:04 ` Thien-Thi Nguyen
2010-01-14 19:53 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871vhuwh6r.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=bug-guile@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).