…is sufficient to build the system.
…LVM GCC and improve remote building
…created directly with gsc.
…blem on Solaris, at least).
… Pierard for spotting this problem).
1) --enable-symlinks configure option (on by default) 2) --enable-multiple-versions configure option (off by default) 3) --enable-absolute-shared-libs configure option (on by default) 4) support for DESTDIR at "make install" 5) support for --bindir=BINDIR, --libdir=LIBDIR, ... 6) Gambit runtime option -:~~bin=BINDIR to override installation directory 7) ~~bin expands to BINDIR (or ~~/bin if none was specified) 8) make uninstall removes all the files that were installed (but not all the directories) 9) configure --help is much more accurate (the exception is that some of the directory specification options are not used, such as --pdfdir=...) 10) gsi -:s automatically loads ~~lib/syntax-case
…ource code management.
…ed: gambc-vX_Y_Z-devel.tgz for developers (whose makefiles support "make update") and gambc-vX_Y_Z.tgz for typical users and package maintainers (whose makefiles do not support "make update"). Both versions will be available on the Gambit web site.
…fixed a few issues with the files managed by Mercurial.
… pull" followed by "make update-nopull" and "make". This is convenient for those cases where you don't want to do a pull or want more control over the pull and final make (like choosing the source code repository, or working offline). In most cases "make update" is the thing to do.
…et the latest sources from the Gambit source code repository.
…fter a "hg pull" when the pulled sources are for a newer release (different version number)
… code repository commit for the current sources
…r (gambcgsi and gambcgsc)