Greetings! One other note -- The gnu-build-system branch supports parallel make, but if you use it, be aware that GCL by default will work in the available memory it sees on your system. Without instruction, multiple processes will not coordinate their allocation. There are three environment variables dealing with this:
GCL_MEM_MULTIPLE=fraction -> all processes see ony this fraction of memory. GCL_MEM_BOUND=integer -> all processes see at most (1<<(integer-1)) bytes of memory. Trumps GCL_MEM_MULTIPLE. GCL_MULTIPROCESS_MEMORY_POOL=dir -> all processes will collectively stay within the indicated memory using a lock file gcl_pool placed in dir. This file should be local (i.e. not on nfs) for decent performance. Parallel builds cut the build time down by more than half. The git repository will host the sources at the 'maintainer-clean' level, but as is customary the distribution will ship with generated info documentation so the building user should not need tex/texinfo. One can generate the distribution tarball with make dist. One can check it with make distcheck, which passes at the moment. As stated before, if you build from a git checkout, you should not need autotools, but may need to: touch aclocal.m4 configure.in configure Makefile.am Makefile.in to match the timestamps in the distribution. In this case you will need texinfo to build the documentation. Take care, Raymond Toy <toy.raym...@gmail.com> writes: > On 4/6/25 2:16 PM, Camm Maguire wrote: > > Greetings, and thank you so much for your report! > > I've pushed a fix to git branch gnu-build-system, which will appear in > release 2.7.0 shortly. > > Fantastic! I build 2.7.0 and can confirm the macrolet issue is fixed. > > However, I do have a build issue. I had to run autoconf again because I don’t > have aclocal-1.17. Everything built fine. But then I did make install. When I > run the > installed gcl, it can’t find /usr/lib/gcl-2.7.0/unixport/saved_gcl. I ran > “configure –prefix=$HOME/dev/gcl-2.7.0”. There is saved_gcl in > $HOME/dev/gcl-2.7.0/lib/gcl-2.7.0/unixport/saved_gcl, as I would have > expected. > > Take care, > > David Scherfgen <d.scherf...@googlemail.com> writes: > > Dear GCL developers, > > Here's another bug(?) I encountered. > > The following code works correctly when entering it directly into the REPL. > But compiling it doesn't work correctly. > > Place this in a file bug.lisp: > > (macrolet ((impl (op) `(,op x y))) > (defun add (x y) (impl +))) > > This defines a function add (x y) with the body (+ x y). > Compile it: > > (compile-file "bug.lisp") > > The compiler gives some warnings that already indicate that something is > wrong: > > ; (DEFUN ADD ...) is being compiled. > ;; Warning: The variable X is not used. > ;; Warning: The variable Y is not used. > > Load the compiled file and try to call add: > > (load "bug.o") > (add 3 4) > > The following error is shown: > > Condition in ADD [or a callee]: INTERNAL-SIMPLE-TYPE-ERROR: IMPL is not of > type FUNCTION: > > The compiler failed to expand the impl macro and treated it like a function! > > Tested with GCL 2.6.14. > > Best regards > David Scherfgen > > ​ > -- Camm Maguire c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
