suggest you configure Guile to use the system's C compiler:
CC=cc ./configure
-
-What You Get ==============================================================
-
-The `configure' script examines your system, and adapts Guile to
-compile and run on it.
-
-The `make' command builds several things:
-- An executable file `guile/guile', which is an interactive shell for
- talking with the Guile Scheme interpreter.
-- An object library `libguile/.libs/libguile.a', containing the Guile Scheme
- interpreter, ready to be linked into your programs.
-
-To install Guile, type `make install'. This installs the executable
-and libraries mentioned above, as well as Guile's header files and
-Scheme libraries.
-
-Make also builds shared libraries, on systems that support them.
-Because of the nature of shared libraries, before linking against
-them, you should probably install them; `make install' takes care of
-this.
-
+NetBSD: Perry Metzger says, "Guile will build under NetBSD only using
+ gmake -- the native make will not work. (gmake is in our package
+ system, so this will not be a problem when we packagize 1.3.)"
Flags Accepted by Configure ===============================================
--with-threads --- Build a Guile executable and library that supports
cooperative threading. If you use this switch, Guile will also build
and install the QuickThreads non-preemptive threading library,
-libqt.a, which you will need to link into your programs after
-libguile.a. That is, you should pass the switches -lguile -qt to your
-linker.
-
-Coop threads are not yet thoroughly tested; once they are, they will
-be enabled by default. The interaction with blocking I/O is pretty ad
-hoc at the moment. In our experience, bugs in the thread support do
-not affect you if you don't actually use threads.
+libqthreads, which you will need to link into your programs after
+libguile. When you use `guile-config', you will pick up all
+neccessary linker flags automatically.
-At the moment, threads are known not to work with the NetBSD 1.2
-assembler.
+Cooperative threads are not yet thoroughly tested; once they are, they
+will be enabled by default. The interaction with blocking I/O is
+pretty ad hoc at the moment. In our experience, bugs in the thread
+support do not affect you if you don't actually use threads.
---enable-dynamic-linking --- Build a Guile executable and library
-providing Scheme functions which can load a shared library and
-initialize it, perhaps thereby adding new functions to Guile. This
-feature is not yet thoroughly tested; once it is, it will be enabled
-by default. This option has no effect on systems that do not support
-shared libraries.
+--with-modules --- Guile can dynamically load `plugin modules' during
+runtime, using facilities provided by libtool. Not all platforms
+support this, however. On these platforms, you can statically link
+the plugin modules into libguile when Guile itself is build. XXX -
+how does one specify the modules?
--disable-shared --- Do not build shared libraries. Normally, Guile
will build shared libraries if your system supports them. Guile
in the path as well.
For example, suppose the Guile distribution unpacked into a directory
-called `/home/jimb/guile-snap' (so the full name of this file would be
-`/home/jimb/guile-snap/INSTALL'). Then you might say:
+called `/home/jimb/guile-snap' (so the full name of this INSTALL file
+would be `/home/jimb/guile-snap/INSTALL'). Then you might say, if
+you're using Bash or any other Bourne shell variant,
export GUILE_LOAD_PATH=/home/jimb/guile-snap
-if you're using Bash or any other Bourne shell variant, or
+or if you're using CSH or one of its variants:
setenv GUILE_LOAD_PATH /home/jimb/guile-snap
-if you're using CSH or one of its variants.
-
-If you built Guile in a separate directory from the source tree, then
-you'll need to include your build directory in the GUILE_LOAD_PATH as
-well. For example, if you built in a subdirectory of the source tree
-called `pentium', you might say:
-
- export GUILE_LOAD_PATH=/home/jimb/guile-snap:/home/jimb/guile-snap/pentium
-
-
-Building a Statically Linked Guile ========================================
-
-Sometimes it's useful to build a statically-linked version of the
-Guile executable. It's helpful in debugging, and for producing
-stand-alone executables for distribution to machines you don't
-control.
-
-To do this, set the LDFLAGS environment variable to `-static' before
-you configure, or before you run the `make' command to build the
-executable.
-
Generic Instructions for Building Auto-Configured Packages ================
HCoop / bpt / guile.git / blobdiff