mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-04-30 03:40:34 +02:00
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>
This commit is contained in:
parent
6ea3048785
commit
e744e076fa
1 changed files with 12 additions and 9 deletions
21
README
21
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
|
built executables and libraries to an installation location other than
|
||||||
the one that was specified at build time.
|
the one that was specified at build time.
|
||||||
|
|
||||||
Another possible approach is to set CPPFLAGS and LDFLAGS before
|
Another possible approach is to set CPPFLAGS and LDFLAGS on the
|
||||||
running configure, so that they include -I options for all the
|
configure command-line, so that they include -I options for all the
|
||||||
non-standard places where you have installed header files and -L
|
non-standard places where you have installed header files and -L
|
||||||
options for all the non-standard places where you have installed
|
options for all the non-standard places where you have installed
|
||||||
libraries. This will allow configure and make to find those headers
|
libraries. This will allow configure and make to find those headers
|
||||||
and libraries during the build. The locations found will not be
|
and libraries during the build. E.g.:
|
||||||
hardcoded into the build executables and libraries, so with this
|
|
||||||
approach you will probably also need to set LD_LIBRARY_PATH
|
../configure [...] CPPFLAGS='-I/my/include' LDFLAGS='-L/my/lib'
|
||||||
correspondingly, to allow Guile to find the necessary libraries again
|
|
||||||
at runtime.
|
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 ================================================
|
Required External Packages ================================================
|
||||||
|
@ -93,8 +96,8 @@ Guile requires the following external packages:
|
||||||
Guile's ./configure script uses pkg-config to discover the correct
|
Guile's ./configure script uses pkg-config to discover the correct
|
||||||
compile and link options for libgc. If you don't have pkg-config
|
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
|
installed, or you have a version of libgc that doesn't provide a
|
||||||
.pc file, you can work around this by setting some environment
|
.pc file, you can work around this by setting some variables as
|
||||||
variables before running ./configure:
|
part of the configure command-line:
|
||||||
|
|
||||||
- PKG_CONFIG=true
|
- PKG_CONFIG=true
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue