Knowledge basePlatforms

Bitness has to match the interpreter

A 64-bit interpreter cannot load a 32-bit engine. This is the most common first-run failure in the script packages.

The script packages ship engine binaries for more than one architecture, and the binding loads whichever one you point it at. If the architecture does not match the interpreter the load fails -- usually with an error that describes the symptom rather than the cause.

Check the interpreter first. A 64-bit interpreter needs the 64-bit engine; a 32-bit one needs the 32-bit engine. Mixing them cannot work, and no configuration setting will make it work.

This is a load-time failure, not a licence failure. If the library loads at all, bitness is not your problem and you should read the licensing article instead.

Last updated 2026-09-09.

Related