Yices 2.8.0 installation errata¶
Issued 2026-11-07, revision 4. Read this with the source archive and manual. This revision supersedes the November 6 revision-3 companion, not the archive.
Scope and disposition¶
This companion corrects installation examples, not solver code. It applies to
the unchanged candidate source commit
1fbee54ad4620893f40836a50d74f91d4bf58bb4 and
yices-2.8.0-src.tar.gz with SHA-256
6cd12c21e684744c890ea071b070ad40f4ae9286621cbffc9633b6c75281033e.
The release owner has approved delivering this erratum while retaining the
archive bytes. This is not release acceptance or legal sign-off.
It also applies to the installation guidance in the unchanged doc/manual.pdf
in the source and all three binary archives. In particular, the manual’s
MCSAT / CUDD and Third-Party SAT Solvers / CaDiCaL,
CryptoMiniSat and Kissat subsections contain shared-prefix dependency
installation examples. Use the private replacements below instead of those
sudo make install or sudo install ... /usr/local/... commands.
The manual PDFs themselves have not been edited.
The static-delegate example in doc/COMPILING section 4a uses predictable
/tmp/yices2-static-delegates and /tmp/yices2-static-cadical-kissat
directories. Do not use those assignments. Do not reuse a staging or
installation directory from another build. Use the fresh workspace below
and retain its variable values throughout the example instead.
Fresh workspace¶
Run these commands in a new Bash shell. Replace the first value with an existing directory that you own and trust; it need not be in your home directory. Use an absolute path without whitespace or a colon. These restrictions also apply after resolving directory symlinks. No elevated privileges are needed.
set -eu
YICES_WORK_PARENT="/absolute/path/you/own"
case "$YICES_WORK_PARENT" in
/*) ;;
*) printf '%s\n' 'Choose an absolute work-parent path.' >&2; exit 1 ;;
esac
test -d "$YICES_WORK_PARENT" && test -O "$YICES_WORK_PARENT"
YICES_WORK_PARENT=$(CDPATH= cd -- "$YICES_WORK_PARENT" && pwd -P)
case "$YICES_WORK_PARENT" in
*[[:space:]:]*) printf '%s\n' 'Work-parent path must have no whitespace or colon.' >&2; exit 1 ;;
esac
umask 077
YICES_WORK_ROOT=$(mktemp -d "$YICES_WORK_PARENT/yices-2.8.0.XXXXXXXX")
YICES_PREFIX="$YICES_WORK_ROOT/install"
test ! -e "$YICES_PREFIX" && test ! -L "$YICES_PREFIX"
export YICES_WORK_ROOT YICES_PREFIX
printf 'Fresh workspace: %s\nInstallation prefix: %s\n' "$YICES_WORK_ROOT" "$YICES_PREFIX"
Keep this shell open. Extract a fresh source tree for each build variant;
repeat the setup to allocate a different workspace for another variant.
Do not point YICES_PREFIX at an existing installation.
Private dependency staging¶
Run this setup once, after the fresh-workspace block, before building any optional dependency or staging the static delegates. It deliberately refuses an existing staging directory. Reuse this newly created prefix only for the matching dependencies of this one build variant.
DELEGATE_PREFIX="$YICES_WORK_ROOT/delegates"
mkdir "$DELEGATE_PREFIX" "$DELEGATE_PREFIX/lib" "$DELEGATE_PREFIX/include" "$DELEGATE_PREFIX/bin"
export DELEGATE_PREFIX
For a release-source reproduction, use the dependency archives supplied with
the release and verify them against RELEASE-INPUTS / SHA256SUMS.
Do not substitute the manual’s moving Git branches for those pinned inputs.
Start each component in its own fresh source extraction. The following are
private-prefix replacements for the named manual recipes, not a claim that
all source-build variants or all recipient toolchains have been tested.
CUDD (manual’s MCSAT / CUDD example)¶
In a fresh extraction of cudd-f54f53330364.tar.gz, replace the manual’s
configure/build/install block with:
./configure --prefix="$DELEGATE_PREFIX" CFLAGS=-fPIC
make
make install
CaDiCaL (manual’s Third-Party SAT Solvers / CaDiCaL example)¶
In a fresh extraction of cadical-7b99c07f0bca.tar.gz:
CXXFLAGS=-fPIC ./configure
make
make test
install build/libcadical.a "$DELEGATE_PREFIX/lib"
install -m644 src/ccadical.h "$DELEGATE_PREFIX/include"
The website also installs CaDiCaL’s optional cadical and mobical
programs into $DELEGATE_PREFIX/bin. Yices library linking needs the
archive and matching header above, not those two programs.
CryptoMiniSat (manual’s Third-Party SAT Solvers / CryptoMiniSat example)¶
In a fresh extraction of
cryptominisat-b8c0e44beef0-yices-release.tar.gz, replace the manual’s
configure/build/install block with:
mkdir build
cd build
cmake .. -DENABLE_PYTHON_INTERFACE=OFF \
-DCMAKE_INSTALL_PREFIX="$DELEGATE_PREFIX" -DCMAKE_INSTALL_LIBDIR=lib
make
make install
CMAKE_INSTALL_LIBDIR=lib keeps the library location consistent with the
-L option below, including on systems whose CMake default would be lib64.
This follows the ordinary shared-library recipe. For the three-delegate
static example, use matching static CryptoMiniSat inputs; this shared build
alone does not provide the static archive that example needs.
Kissat (manual’s Third-Party SAT Solvers / Kissat example)¶
In a fresh extraction of kissat-7e08e8703ad7.tar.gz:
./configure -fPIC
make
install build/libkissat.a "$DELEGATE_PREFIX/lib"
install -m644 src/kissat.h "$DELEGATE_PREFIX/include"
Matching Yices lookup and installation¶
For an ordinary Yices configure command, keep its feature defines and
required LIBS, but add -I$DELEGATE_PREFIX/include to CPPFLAGS and
-L$DELEGATE_PREFIX/lib to LDFLAGS. Always retain
--prefix="$YICES_PREFIX" for Yices itself. For example, after separately
building matching position-independent LibPoly and CUDD into the dependency
prefix, the manual’s MCSAT-only Yices command becomes:
./configure --prefix="$YICES_PREFIX" --enable-mcsat \
CPPFLAGS="-I$DELEGATE_PREFIX/include" LDFLAGS="-L$DELEGATE_PREFIX/lib"
make -j
make install
Use the supplied LibPoly source and its build instructions or the matching
relink kit’s REBUILDING.md; LibPoly is not built by the CUDD commands.
If a dependency is in another private prefix, add that prefix’s matching
include and library directories as well. Shared dependencies must also be
found by the runtime loader: -L alone does not set its search path.
Keep dependency prefixes for as long as the installed program needs them.
The static-only two-/three-delegate routes below have different targets;
do not apply this ordinary make / make install sequence to them.
Static-delegate example correction and configuration labels¶
Two-delegate variant: doc/COMPILING section 4a configures CaDiCaL
plus Kissat; it does not enable CryptoMiniSat. Continue section 4a using the
fresh prefix values above, skipping both of its old /tmp
assignments. Preserve the documented -I/-L options and the
--with-static-delegates options. Use make static-bin, not bare
make or make all, for that raw CaDiCaL-plus-Kissat configuration.
Do not run make install after make static-bin: follow section 4a’s
explicit copies from static_bin into the new $YICES_PREFIX/bin.
On macOS, retain its requirement for the matching configured Kissat source
tree and KISSAT_SOURCE_DIR. Do not overwrite these fresh prefix values
with /usr/local later in the example.
Three-delegate variant: the website’s explicitly labeled static example
adds CryptoMiniSat to CaDiCaL and Kissat. Its extra
-DHAVE_CRYPTOMINISAT and -lcryptominisat5 are intentional, not
corrections to the two-delegate archive example. It requires the additional
matching static CryptoMiniSat library and headers. Both variants use the
same private-prefix setup and static-only installation precautions. For
the complete release configuration and replacement-library workflow, use
the matching relink kit and its supplied dependency inputs/instructions.
Ordinary source and binary installations¶
For an ordinary, non-static-only source build, pass
--prefix="$YICES_PREFIX" to ./configure, then build and use
make install without sudo. Source ``make install`` has no collision
protection and can overwrite existing Yices files without prompting.
Without --prefix its default is /usr/local. A shared-prefix replacement
is a separate, deliberate administrative action requiring backups; it is
not the installation example recommended here.
Changing a protected system-owned prefix requires the appropriate authorized
privileges, which may mean administrator/root access. Do not elevate privileges
merely to bypass a collision or a failed fresh-prefix check.
For a prebuilt binary archive, run ./install-yices "$YICES_PREFIX"
from the freshly extracted archive, without sudo. Its refusal to overwrite
existing Yices files is separate from source make install. Do not use
the installer’s replacement option as a workaround for an unexpected
collision; choose a fresh prefix and inspect the existing files instead.
An explicitly labeled administrative --replace-existing /usr/local
example in a binary README is a separate opt-in replacement operation,
not the default fresh-prefix route. Back up the existing installation and
confirm exactly what will be replaced before choosing that operation.
This erratum does not prohibit deliberate system administration; it prevents
confusing that choice with a protected or fresh installation.
Package managers and documentation tools¶
Commands such as sudo apt-get install install system-managed prerequisites
or packages and intentionally affect shared locations. They are not source
make install commands and do not acquire the binary installer’s collision
protection. Review the package manager’s proposed changes or ask your system
administrator; do not run them merely to bypass a fresh-prefix failure.
The SRI Homebrew formula is SRI-CSL/sri-csl/yices2, not yices.
On 2026-11-06 the formula selected Yices 2.7.0. The Ubuntu PPA may also lag;
no new PPA package is part of the 2.8.0 release. Check the selected version
before using either route. Use the matching official archives for 2.8.0.
The manual’s bare pip install sphinx is not a command to modify a system
or existing user Python environment. Build API documentation in a new
virtual environment using the website source’s requirements-publish.lock
and doc/sphinx/README.md. The checked publication profile uses Sphinx
9.1.0; the lock and website source are companion materials, not extra members
of the unchanged release source archive.
Separately maintained Python and Go bindings¶
The manual’s bare pip install yices example is not an instruction to change
the system Python or an existing user environment. Use a new, dedicated Python
virtual environment for the separately maintained Python bindings.
For the separately maintained Go bindings, use a fresh, separate Go module/work context and a deliberately chosen installation location, not an existing project or a shared installation. Follow the bindings’ own documentation for commands appropriate to the binding and Go versions you select.
These are isolation precautions, not new tested binding-install recipes. The Python and Go binding repositories are respectively https://github.com/SRI-CSL/yices2_python_bindings and https://github.com/SRI-CSL/yices2_go_bindings. This companion does not install or test either binding, or replace their version-specific documentation.
Delivery requirement¶
Keep this file with the source archive and review/test packets. The source
download page and documentation page must link to it before publication.
The required source is the generated yices-2.8.0-src.tar.gz identified
above, not GitHub’s automatically generated tag archive. A repository/tag
browser link is useful for source history but does not establish identical
distribution bytes or supply all generated release inputs.
It does not claim that the unchanged archive contains the corrected example,
that earlier reviewer findings were withdrawn, or that publication gates
have passed.
Download the same companion as
YICES-2.8.0-INSTALLATION-ERRATA.txt.