{"id":13792647,"url":"https://github.com/texmacs/guile","last_synced_at":"2025-05-12T14:32:03.202Z","repository":{"id":86967280,"uuid":"153005985","full_name":"texmacs/guile","owner":"texmacs","description":"mirror of GNU Guile","archived":false,"fork":false,"pushed_at":"2020-08-15T14:22:04.000Z","size":49636,"stargazers_count":9,"open_issues_count":4,"forks_count":6,"subscribers_count":5,"default_branch":"msvc_1-8-8","last_synced_at":"2024-11-18T06:49:33.246Z","etag":null,"topics":["gnu","guile"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/texmacs.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING.LESSER","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS"}},"created_at":"2018-10-14T18:33:34.000Z","updated_at":"2024-06-13T14:36:41.000Z","dependencies_parsed_at":"2023-03-13T19:48:50.316Z","dependency_job_id":null,"html_url":"https://github.com/texmacs/guile","commit_stats":null,"previous_names":[],"tags_count":4,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/texmacs%2Fguile","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/texmacs%2Fguile/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/texmacs%2Fguile/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/texmacs%2Fguile/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/texmacs","download_url":"https://codeload.github.com/texmacs/guile/tar.gz/refs/heads/msvc_1-8-8","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253754968,"owners_count":21958934,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["gnu","guile"],"created_at":"2024-08-03T22:01:14.699Z","updated_at":"2025-05-12T14:32:01.269Z","avatar_url":"https://github.com/texmacs.png","language":"C","funding_links":[],"categories":["For Developers"],"sub_categories":[],"readme":"This is version 1.8.7 of Guile, Project GNU's extension language\nlibrary.  Guile is an interpreter for Scheme, packaged as a library\nthat you can link into your applications to give them their own\nscripting language.  Guile will eventually support other languages as\nwell, giving users of Guile-based applications a choice of languages.\n\nPlease send bug reports to bug-guile@gnu.org.\n\nSee the LICENSE file for the specific terms that apply to Guile.\n\n\nAdditional INSTALL instructions ===========================================\n\nGeneric instructions for configuring and compiling Guile can be found\nin the INSTALL file.  Guile specific information and configure options\ncan be found below, including instructions for installing SLIB.\n\nGuile requires a few external packages and can optionally use a number\nof external packages such as `readline' when they are available.\nGuile expects to be able to find these packages in the default\ncompiler setup, it does not try to make any special arrangements\nitself.  For example, for the `readline' package, Guile expects to be\nable to find the include file \u003creadline/readline.h\u003e, without passing\nany special `-I' options to the compiler.\n\nIf you installed an external package, and you used the --prefix\ninstallation option to install it somewhere else than /usr/local, you\nmust arrange for your compiler to find it by default.  If that\ncompiler is gcc, one convenient way of making such arrangements is to\nuse the --with-local-prefix option during installation, naming the\nsame directory as you used in the --prefix option of the package.  In\nparticular, it is not good enough to use the same --prefix option when\nyou install gcc and the package; you need to use the\n--with-local-prefix option as well.  See the gcc documentation for\nmore details.\n\n\nRequired External Packages ================================================\n\nGuile requires the following external packages:\n\n  - GNU MP, at least version 4.1\n\n    GNU MP is used for bignum arithmetic.  It is available from\n    http://swox.com/gmp\n\n  - libltdl from libtool, at least from libtool version 1.5.6\n\n    libltdl is used for loading extensions at run-time.  It is\n    available from http://www.gnu.org/software/libtool/\n\n\nGuile specific flags Accepted by Configure =================================\n\nIf you run the configure script with no arguments, it should examine\nyour system and set things up appropriately.  However, there are a few\nswitches specific to Guile you may find useful in some circumstances.\n\n--without-threads  ---  Build without thread support\n\n  Build a Guile executable and library that supports multi-threading.\n\n  The default is to enable threading support when your operating\n  system offsers 'POSIX threads'.  When you do not want threading, use\n  `--without-threads'.\n\n--enable-deprecated=LEVEL\n\n  Guile may contain features that are `deprecated'.  When a feature is\n  deprecated, it means that it is still there, but that there is a\n  better way of achieving the same thing, and we'd rather have you use\n  this better way.  This allows us to eventually remove the old\n  implementation and helps to keep Guile reasonably clean of historic\n  baggage.\n\n  Deprecated features are considered harmful; using them is likely a\n  bug.  See below for the related notion of `discouraged' features,\n  which are OK but have fallen out of favor.\n\n  See the file NEWS for a list of features that are currently\n  deprecated.  Each entry will also tell you what you should replace\n  your code with.\n\n  To give you some help with this process, and to encourage (OK,\n  nudge) people to switch to the newer methods, Guile can emit\n  warnings or errors when you use a deprecated feature.  There is\n  quite a range of possibilities, from being completely silent to\n  giving errors at link time.  What exactly happens is determined both\n  by the value of the `--enable-deprecated' configuration option when\n  Guile was built, and by the GUILE_WARN_DEPRECATED environment\n  variable.\n\n  It works like this:\n\n    When Guile has been configured with `--enable-deprecated=no' (or,\n    equivalently, with `--disable-deprecated') then all deprecated\n    features are omitted from Guile.  You will get \"undefined\n    reference\", \"variable unbound\" or similar errors when you try to\n    use them.\n\n    When `--enable-deprecated=LEVEL' has been specified (for LEVEL not\n    \"no\"), LEVEL will be used as the default value of the environment\n    variable GUILE_WARN_DEPRECATED.  A value of \"yes\" is changed to\n    \"summary\" and \"shutup\" is changed to \"no\", however.\n\n    When GUILE_WARN_DEPRECATED has the value \"no\", nothing special\n    will happen when a deprecated feature is used.\n\n    When GUILE_WARN_DEPRECATED has the value \"summary\", and a\n    deprecated feature has been used, Guile will print this message at\n    exit:\n\n      Some deprecated features have been used.  Set the environment\n      variable GUILE_WARN_DEPRECATED to \"detailed\" and rerun the\n      program to get more information.  Set it to \"no\" to suppress\n      this message.\n\n    When GUILE_WARN_DEPRECATED has the value \"detailed\", a detailed\n    warning is emitted immediatly for the first use of a deprecated\n    feature.\n\n  The default is `--enable-deprecated=yes'.\n\n  In addition to setting GUILE_WARN_DEPRECATED in the environment, you\n  can also use (debug-enable 'warn-deprecated) and (debug-disable\n  'warn-deprecated) to enable and disable the detailed messaged at run\n  time.\n\n--disable-discouraged\n\n  In addition to deprecated features, Guile can also contain things\n  that are merely `discouraged'.  It is OK to continue to use these\n  features in old code, but new code should avoid them since there are\n  better alternatives.\n\n  There is nothing wrong with a discouraged feature per se, but they\n  might have strange names, or be non-standard, for example.  Avoiding\n  them will make your code better.\n\n--disable-shared  ---  Do not build shared libraries.\n--disable-static  ---  Do not build static libraries.\n\n  Normally, both static and shared libraries will be built if your\n  system supports them.\n\n--enable-debug-freelist  ---  Enable freelist debugging.\n\n  This enables a debugging version of scm_cell and scm_double_cell,\n  and also registers an extra primitive, the setter\n  `gc-set-debug-check-freelist!'.\n\n  Configure with the --enable-debug-freelist option to enable the\n  gc-set-debug-check-freelist! primitive, and then use:\n\n  (gc-set-debug-check-freelist! #t)  # turn on checking of the freelist\n  (gc-set-debug-check-freelist! #f)  # turn off checking\n\n  Checking of the freelist forces a traversal of the freelist and a\n  garbage collection before each allocation of a cell.  This can slow\n  down the interpreter dramatically, so the setter should be used to\n  turn on this extra processing only when necessary.\n\n--enable-debug-malloc  ---  Enable malloc debugging.\n\n  Include code for debugging of calls to scm_malloc, scm_realloc, etc.\n\n  It records the number of allocated objects of each kind.  This is\n  useful when searching for memory leaks.\n\n  A Guile compiled with this option provides the primitive\n  `malloc-stats' which returns an alist with pairs of kind and the\n  number of objects of that kind.\n\n--enable-guile-debug  ---  Include internal debugging functions\n--disable-posix       ---  omit posix interfaces\n--disable-networking  ---  omit networking interfaces\n--disable-regex       ---  omit regular expression interfaces\n\n\nCross building Guile  =====================================================\n\nGuile can be cross-compiled for Windows using the i586-mingw32msvc\ncross-compiler.  To do this, you first need to cross-build Guile's\nprerequisites - GNU MP and libtool/libltdl (as described above) - and\nthen cross-build Guile itself.\n\nFor each of these steps, configure using an invocation like this:\n\nCPPFLAGS=-I/usr/local/i586-mingw32msvc/include \\\nLDFLAGS=-L/usr/local/i586-mingw32msvc/lib \\\nGUILE_FOR_BUILD=/usr/local/bin/guile \\\n./configure --prefix=/usr/local/i586-mingw32msvc --host=i586-mingw32msvc\n\nThen run `make' - which should complete without any errors - and `sudo\nmake install'.  (`make check' doesn't work when cross-compiling,\nbecause the built DLLs and program cannot be run on GNU/Linux.)\n\nThe `GUILE_FOR_BUILD=...' setting is needed because some later steps\nof the build process use Guile itself.  In the non-cross-compiling\ncase this is the version of Guile that has just been built.  When\ncross-compiling, you have to set GUILE_FOR_BUILD to tell the build\nwhere it can find a native version of Guile, to use for these steps.\n\nCross-compiling for other hosts may also work, using the following\ninstructions; but this has not been recently tested.\n\nTo configure Guile for cross building, for example for Cygwin:\n\n    ./configure --host=i686-pc-cygwin --disable-shared\n\nA C compiler for the build system is required.  The default is\n\"PATH=/usr/bin:$PATH cc\".  If that doesn't suit it can be specified\nwith the CC_FOR_BUILD variable in the usual way, for instance\n\n    ./configure --host=m68k-unknown-linux-gnu CC_FOR_BUILD=/my/local/gcc\n\nGuile for the build system can be specified similarly with the\nGUILE_FOR_BUILD variable, it defaults to just \"guile\".\n\n\nUsing Guile Without Installing It =========================================\n\nThe top directory of the Guile sources contains a script called\n\"pre-inst-guile\" that can be used to run the Guile that has just been\nbuilt.\n\n\nInstalling SLIB ===========================================================\n\nIn order to use SLIB from Guile you basically only need to put the\n`slib' directory _in_ one of the directories on Guile's load path.\n\nThe standard installation is:\n\n  1. Obtain slib from http://www-swiss.ai.mit.edu/~jaffer/SLIB.html\n\n  2. Put it in Guile's data directory, that is the directory printed when\n     you type\n\n       guile-config info pkgdatadir\n\n     at the shell prompt.  This is normally `/usr/local/share/guile', so the\n     directory will normally have full path `/usr/local/share/guile/slib'.\n\n  3. Start guile as a user with write access to the data directory and type\n\n       (use-modules (ice-9 slib))\n\n     at the Guile prompt.  This will generate the slibcat catalog next to\n     the slib directory.\n\nSLIB's `require' is provided by the Guile module (ice-9 slib).\n\nExample:\n\n  (use-modules (ice-9 slib))\n  (require 'primes)\n  (prime? 7)\n\n\nGuile Documentation ==================================================\n\nIf you've never used Scheme before, then the Guile Tutorial\n(guile-tut.info) is a good starting point.  The Guile Reference Manual\n(guile.info) is the primary documentation for Guile.  The Goops object\nsystem is documented separately (goops.info).  A copy of the R5RS\nScheme specification is included too (r5rs.info).\n\nInfo format versions of this documentation are installed as part of\nthe normal build process.  The texinfo sources are under the doc\ndirectory, and other formats like Postscript, PDF, DVI or HTML can be\ngenerated from them with Tex and Texinfo tools.\n\nThe doc directory also includes an example-smob subdirectory which has\nthe example code from the \"Defining New Types (Smobs)\" chapter of the\nreference manual.\n\nThe Guile WWW page is at\n\n  http://www.gnu.org/software/guile/guile.html\n\nIt contains a link to the Guile FAQ.\n\nAbout This Distribution ==============================================\n\nInteresting files include:\n\n- LICENSE, which contains the exact terms of the Guile license.\n- COPYING, which contains the terms of the GNU General Public License.\n- INSTALL, which contains general instructions for building/installing Guile.\n- NEWS, which describes user-visible changes since the last release of Guile.\n\nFiles are usually installed according to the prefix specified to\nconfigure, /usr/local by default.  Building and installing gives you:\n\nExecutables, in ${prefix}/bin:\n\n guile --- a stand-alone interpreter for Guile.  With no arguments, this\n \tis a simple interactive Scheme interpreter.  It can also be used\n \tas an interpreter for script files; see the NEWS file for details.\n guile-config --- a Guile script which provides the information necessary\n \tto link your programs against the Guile library.\n guile-snarf --- a script to parse declarations in your C code for\n \tScheme-visible C functions, Scheme objects to be used by C code,\n \tetc.\n\nLibraries, in ${prefix}/lib.  Depending on the platform and options\n        given to configure, you may get shared libraries in addition\n\tto or instead of these static libraries:\n\n libguile.a --- an object library containing the Guile interpreter,\n \tYou can use Guile in your own programs by linking against this.\n libguilereadline.a --- an object library containing glue code for the\n        GNU readline library.\n\n libguile-srfi-*.a --- various SRFI support libraries\n\nHeader files, in ${prefix}/include:\n\n libguile.h, guile/gh.h, libguile/*.h --- for libguile.\n guile-readline/readline.h --- for guile-readline.\n\nSupport files, in ${prefix}/share/guile/\u003cversion\u003e:\n\n ice-9/* --- run-time support for Guile: the module system,\n \tread-eval-print loop, some R4RS code and other infrastructure.\n oop/* --- the Guile Object-Oriented Programming System (GOOPS)\n scripts/* --- executable modules, i.e., scheme programs that can be both\n \tcalled as an executable from the shell, and loaded and used as a\n \tmodule from scheme code.  See scripts/README for more info.\n srfi/* --- SRFI support modules.  See srfi/README for more info.\n\nAutomake macros, in ${prefix}/share/aclocal:\n\n guile.m4\n\nDocumentation in Info format, in ${prefix}/info:\n\n guile --- Guile reference manual.\n\n guile-tut --- Guile tutorial.\n\n GOOPS --- GOOPS reference manual.\n\n r5rs --- Revised(5) Report on the Algorithmic Language Scheme.\n\n\nThe Guile source tree is laid out as follows:\n\nlibguile:\n\tThe Guile Scheme interpreter --- both the object library\n\tfor you to link with your programs, and the executable you can run.\nice-9:  Guile's module system, initialization code, and other infrastructure.\nguile-config:\n\tSource for the guile-config script.\nguile-readline:\n        The glue code for using GNU readline with Guile.  This\n        will be build when configure can find a recent enough readline\n        library on your system.\ndoc:\tDocumentation (see above).\n\nGit Repository Access ================================================\n\nGuile's source code is stored in a Git repository at Savannah.  Anyone\ncan access it using `git-clone' from one of the following URLs:\n\n  git://git.sv.gnu.org/guile.git\n  http://git.sv.gnu.org/r/guile.git\n\nDevelopers with a Savannah SSH account can also access it from:\n\n  ssh://git.sv.gnu.org/srv/git/guile.git\n\nThe repository can also be browsed on-line at the following address:\n\n  http://git.sv.gnu.org/gitweb/?p=guile.git\n\nFor more information on Git, please see:\n\n  http://git.or.cz/\n\nPlease send problem reports to \u003cbug-guile@gnu.org\u003e.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftexmacs%2Fguile","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftexmacs%2Fguile","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftexmacs%2Fguile/lists"}