# InductEx® or TetraHenry® fails on Linux with a runtime-library error

Check the failing executable and its required runtime against the supported package target. A newer OS name or copied binary does not guarantee ABI compatibility.

## Compatibility

Exact OS, architecture and package build apply

Published guidance with release-applicability limits. Confirm package applicability before following this guide.

## Identify the failing component

1. Record the full missing-library or GLIBC/GLIBCXX diagnostic, OS release, CPU architecture and InductEx®/TetraHenry® package versions.
2. Determine whether Core, Studio or the numerical engine fails. A frontend can start while an engine fails when invoked.
3. Use the supported package for that OS/architecture, including its matching engine and runtime dependencies.
4. 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.

## Related guides

- [Move software to another machine, OS or execution account](/knowledge-base/shared-moving-a-licence)
- [Prepare a useful support report without exposing a licence or private design](/knowledge-base/support-effective-report)