Compatibility
Exact OS, architecture and package build apply
Package applicability is under review; follow the stated version and platform limits.
Exact OS, architecture and package build apply
Package applicability is under review; follow the stated version and platform limits.
Identify the failing component
- Record the full missing-library or GLIBC/GLIBCXX diagnostic, OS release, CPU architecture and InductEx®/TetraHenry® package versions.
- Determine whether Core, Studio or the numerical engine fails. A frontend can start while an engine fails when invoked.
- Use the supported package for that OS/architecture, including its matching engine and runtime dependencies.
- Ask support for a compatible build when the published target does not match. Do not replace system libc or mix unrelated engine binaries as a generic workaround.
Keep historical fixes narrow
Support history contains successful targeted Linux rebuilds and a specifically supplied static engine for an older release. Those outcomes establish that particular combination, not compatibility of every current package with older Linux distributions.
A successful launch should be followed by a small licensed example and output check before production work.
Sources and verification details
Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.
- support:SUP-005 · Generalised editorial finding; outcome qualification retained
- inductex:docs/manual/ix_install.tex · Linux installation
- Support history informed this draft. Current-source guidance has been checked; a fresh walkthrough on the intended distributed release and product-owner review remain pending.