Libffi Tests Use Correct Include Paths for Multilib Targets
Libffi tests now use the correct include paths when building for multilib targets, fixing include errors.
The libffi testsuite previously used relative include paths, causing issues when run from the main target build directory in multilib configurations. This commit fixes the problem by using variables that point to the build directory for the specific multilib variant being tested. This ensures that the tests include the correct files, avoiding build failures in multilib setups.
In Details
Libffi's testsuite uses relative include paths, which breaks when tests are run from a different directory, especially in multilib builds. The fix replaces these paths with ${libffi_include} and ${blddirffi} in testsuite/lib/libffi.exp, so the include paths are correct regardless of the current directory.
For Context
Libffi is a library that provides a portable way to call functions written in other languages. It's often used in environments where different parts of a system are written in different languages and need to communicate with each other. When building libffi for multiple architectures (multilib), the build process organizes files in a specific directory structure. This change ensures that the libffi tests can find the necessary header files in this structure, preventing build errors.