From a34cd56c13b00a8e17c4c55ce46d15ea79636c65 Mon Sep 17 00:00:00 2001 From: Matt Birkholz Date: Wed, 25 May 2016 16:12:31 -0700 Subject: [PATCH] gdbm/README: Update with automake build process. --- src/gdbm/README | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/src/gdbm/README b/src/gdbm/README index 3bacf4c61..026692005 100644 --- a/src/gdbm/README +++ b/src/gdbm/README @@ -2,17 +2,16 @@ The GDBM option. This is a drop-in replacement for the gdbm microcode module and runtime/gdbm.scm. It is not part of the core build and can be built -outside the core build tree. There is no ./configure script yet. If -you know you have libgdbm installed, you should win with this command: +outside the core build tree in the customary way: + ./configure [--with-openssl=directory]... make all check install The install target copies a shared library shim and compiled Scheme -files into the system library path, and re-writes the optiondb.scm +files into the system library path and re-writes the optiondb.scm found there. You can override the default command name "mit-scheme" (and thus the system library path) by setting MIT_SCHEME_EXE. -The option is currently called GDBM2 until GDBM no longer refers to -the original microcode module. You will need to import the bindings -you want to use. They are not exported to the global environment -because they would conflict with the exports from (runtime gdbm). +To use: (load-option 'GDBM2) and import the bindings you want. They +are not exported to the global environment because they would conflict +with the exports from (runtime gdbm). -- 2.25.1