Hi Arthur,
after upgrading my MacBook Air M1 to macOS Ventura 13.6, the file "trunk/scripts/run.sh" cannot find any more the version of csl-reduce compiled after configuring with
"./configure --with-csl --enable-universal".
The script "run.sh" expects to find the compiled files in the directory
"trunk/cslbuild/aarch64-mac_13_ventura-darwin22.6.0"
while they have been compiled in the directory
"trunk/cslbuild/universal-mac_13_ventura-darwin22.6.0".
Commenting out the test
if ! test -x $here/../cslbuild/$host$version/csl/$ap
then
version="$version-nogui"
fi
everything works fine.
No problem when I compile after configuring with "./configure --with-csl"
Best regards
Marco Ferraris
So let me check a detail first....
When you configure and build the CSL version of Reduce the files are
placed in a directory with a name like aarch64-mac_13_ventura-darwin22.6.0
as you observe. On the Mac that is the extra complication of aarch64 vs
amd64 vs universal and each of those goes in a different place. The "run"
script checks the current operating system version and looks for a
directory whose name matches it. So when you update your OS eg in a way
where the darwin version changes the existing files cease to be found and
you are expected to need to configure and build again. It is sone that way
because there is no guarantee of compatibility when the OS version changes
- or at least I am extra neurotic about that possibility.
so if you upgrade the OS (or Apple does so under your feet without asking
you!) you may need to do
./configure --with-csl
./configure --with-csl --enable-universal
make
before the world is happy again. And then you may want to delete the old
builds.
Maybe I messed something up when I put in the "better" support for the
"-nogui" option which is for the pathalogical case where somebody has
build "--wthout-gui" but not in "regular" form. I stuck that in because
termux (linux on an Android phone/tablet) does not support a GUI...
I will look at that.
Does this help explain some of what may be going on?
Arthur
On Sat, 23 Sep 2023, Marco Ferraris wrote:
Related
Bugs: #154