-
Notifications
You must be signed in to change notification settings - Fork 436
Description
Summary
Building OpenROAD-flow-scripts on Kali GNU/Linux fails at multiple stages due to OS detection not recognizing Kali (or generic Debian derivatives). Since Kali is Debian-based, it should be routed through the existing Debian/Ubuntu installation paths.
Issues Encountered
-
OS detection failure — Both
etc/DependencyInstaller.shandtools/OpenROAD/etc/DependencyInstaller.shonly match"Ubuntu","Debian GNU/Linux rodete", and"Debian GNU/Linux"exactly. Kali reports its OS as"Kali GNU/Linux", causing an "unsupported system" error. -
libtclvirtual package — On Kali (and some Debian versions),libtclis a virtual package with no install candidate. The script needs to fall back tolibtcl8.6. -
Hardcoded
libpython3.8— The Debian install path defaults tolibpython3.8, which doesn't exist on newer Debian-based distros (Kali has Python 3.13+). The version should be auto-detected. -
or-tools download URL — Kali's
VERSION_IDis2025.4, which doesn't correspond to any or-tools release. Non-standard Debian version IDs need to be normalized to a compatible Debian release (e.g.,12). -
Abseil compiled without
-fPIC— On GCC 15 (Kali/Debian Testing), PIE is the default. Abseil static libraries need-DCMAKE_POSITION_INDEPENDENT_CODE=ONto link into PIE executables.
Environment
- OS: Kali GNU/Linux 2025.4 (Rolling, based on Debian Testing)
- GCC: 15.2.0
- glibc: 2.42
- Python: 3.13
Expected Behavior
setup.sh and build_openroad.sh should complete successfully on Kali and other Debian derivatives.