Hi Francis.
1) This applies to Common Lisp Reduce revision 7171, and all previous revisions.
Compiling Common Lisp Reduce and running ./redsbcl one gets this kind of output
REDUCE (Free SBCL version, revision 7167), 10-Jan-2026 ...
1:
This is the correct expected behaviour, even if revision should be 7171 instead of 7167.
2) This applies to Common Lisp Reduce revision 7172, and all subsequent revisions.
Compiling Common Lisp Reduce and running ./redsbcl one gets this kind of output
REDUCE (Free SBCL version, revision ???), build date 10-Jan-2026 ...
1:
This is not the correct behaviour because revision should be 7172 instead of ???.
Best regards, Marco.
I don't see this problem on Windows. For a version I built yesterday on SBCL I see
What platform are you running on?
revision ??? means that the build script could not automatically determine the Subversion revision number. What happens if you go into the
packagesdirectory that you are using for your build and runI currently get (on Cygwin)
Francis
On my 'Windows 11 Home (25H2)' X86_64 laptop I tested the old revions of Reduce I found in a backup disk. Compiling and running Common Lisp Reduce I got the following results:
i) SBCL Common Lisp Reduce r7204, r7205, r7213, r7246, r7251
This seems to suggest that there is some difference between the 7246 revision I downloaded today and the one you used.
ii) CLISP Common Lisp Reduce r7204, r7213, r7246, r7251
iii) CCL Common Lisp Reduce r7204, r7213, r7246
To compile Common Lisp Reduce (in Cygwin) I used SBCL 2.4.7, CLISP 2.42.92 and CCL64 1.12.1.
Marco
It would be useful to know what output is produced by running
svnversion. (Please see my previous message.)What does the top of the output from a build look like? It should look something like this:
If you don't see the line about the revision number then it is not being set automatically. (There is no warning if it is not set automatically, but I will fix that.) For automatic version detection, you need to build within a REDUCE file tree that it under Subversion control, i.e. has a directory
.svnin the root (orpackages) directory.Francis
Hi Francis,
I did not understand why you insisted in asking me the result of 'svnversion'. Now I understand why: you want to use the command 'svnversion' to set the value of the variable 'revision!*'.
Using 'svnversion' to set the value of the variable 'revision!*' as you do in the (e.g. r7253) file 'build.sh' works only if you are using a 'trunk' directory obtained by downloading reduce-algebra code using the standard checkout command
(or an 'svn update' of a previously checked out 'trunk' directory) and then you build the Common Lisp versions in the directory
However, if you download the snapshot of a Reduce code revision and you try to build Common Lisp Reduce in the directory 'reduce-algebra-code-rnnnn-trunk/common-lisp', or if you try to build Common Lisp Reduce in an alternative build directory as I did, 'svnversion' will fail because the '.svn' directories are missing.
Please remember that the method to set the value of the variable 'revision!*' used in r7171 'build.sh' (and previous revisions) was perfectly good.
In order to have a working Common Lisp Reduce version I had to comment out line 30 of the file 'sl-on-cl.lisp'
Marco
I think it would be reasonable to parse the revision number out of the root directory name, so I'll think about doing that as a fall-back. I occasionally commit a version of
sl-on-clconfigured for debugging by mistake. (It should work, but it will be slow and balk on errors more than you might want.) I think I can provide a better way of controlling this, which will mean I can't commit the wrong version, so I'll also think about that. Thanks for a couple of useful ideas.Francis
My latest commit should fix both the issues about revision numbers and committing versions with debugging enabled.
Building r7257 and r5278 Common Lisp Reduce on macOS fails, because 'bash' does not digest the following commands:
I changed them as follows
and there was not any problem in building.
The 'bash' versions are
and
Up to r5274 there was not any problem in building.
Marco
OK, I'll stop using the -v operator. However, I think you've found a bug in the version of bash that you're using, which would be worth reporting. The -v operator works for me in bash 5.2 on Cygwin and Ubuntu, and it's described in the current online documentation for bash 5.3.
Francis
From: bugs@reduce-algebra.p.re.sourceforge.net bugs@reduce-algebra.p.re.sourceforge.net on behalf of Marco Ferraris marcoferraris@users.sourceforge.net
Sent: Friday, January 16, 2026 4:46 PM
To: [reduce-algebra:bugs] 188@bugs.reduce-algebra.p.re.sourceforge.net
Subject: [reduce-algebra:bugs] #188 Wrong Common Lisp Reduce header message
Building r7257 and r5278 Common Lisp Reduce on macOS fails, because 'bash' does not digest the following commands:
[ -v lisp ] || ...
if [ -v clean ]; then ...
[ -v debug ] ...
if [ ! -v reduce ]; then ...
if [ ! -v revision ]
if [ -v bootstraponly ]
if [ -v coreonly ]
I changed them as follows
[ -n "$lisp" ] ||
if [ -n "$clean" ]; then
[ -n "$debug" ] ...
if [ -z "$reduce" ]
if [ -z "$revision" ]
if [ -n "$bootstraponly" ]
if [ -n "$coreonly" ]
and there was not any problem in building.
The 'bash' versions are
bash --version
GNU bash, versione 5.3.3(1)-release (x86_64-apple-darwin20.6.0)
and
bash --version
GNU bash, versione 5.3.3(1)-release (aarch64-apple-darwin25.1.0)
Up to r5274 there was not any problem in building.
Marco
[bugs:#188]https://sourceforge.net/p/reduce-algebra/bugs/188/ Wrong Common Lisp Reduce header message
Status: closed
Group:
Labels: Common Lisp revision
Created: Sat Jan 10, 2026 06:57 PM UTC by Marco Ferraris
Last Updated: Wed Jan 14, 2026 11:20 AM UTC
Owner: Francis Wright
Hi Francis.
1) This applies to Common Lisp Reduce revision 7171, and all previous revisions.
Compiling Common Lisp Reduce and running ./redsbcl one gets this kind of output
REDUCE (Free SBCL version, revision 7167), 10-Jan-2026 ...
1:
This is the correct expected behaviour, even if revision should be 7171 instead of 7167.
2) This applies to Common Lisp Reduce revision 7172, and all subsequent revisions.
Compiling Common Lisp Reduce and running ./redsbcl one gets this kind of output
REDUCE (Free SBCL version, revision ???), build date 10-Jan-2026 ...
1:
This is not the correct behaviour because revision should be 7172 instead of ???.
Best regards, Marco.
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/reduce-algebra/bugs/188/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Bugs:
#188Just informational:
The current bash version on MacOS 26.2 is:
sturm@vir-2/1[~] /bin/bash --version
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin25)
Copyright (C) 2007 Free Software Foundation, Inc.
It seems that this is not updated anymore for license reasons. I do no not remember details - it might be problems with GPL 3.
My personal solution is to have an up-to-date /opt/local/bin/bash via Macports in my path first but still use the old Apple bash as a login shell.
sturm@vir-2/1[~] bash --version
GNU bash, version 5.2.37(1)-release (aarch64-apple-darwin24.3.0)
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
Best,
Thomas
Related
Bugs:
#188Hi Thomas, you are right!
When I tested bash version number I did it by using the command bash --version (which corresponds to /opt/local/bin/bash --version) instead of using the command /bin/bash --version.
I verified it just now that using #!/opt/local/bin/bash instead of #!/bin/bash as first line in the file r5259 build.sh works fine.
Best regards
Marco
Apologies!
Of course r5259 should be replaced by r7258.