John Cowan wrote:
Brandon J. Van Every scripsit:
Or, why use a system libffi. If it's that bad, it would be safer to
put a "known good" version in Chicken itself, as we do with PCRE.
Because it has to be synchronized with gcc; it has intimate knowledge
of gcc's calling conventions on the particular platform. Much of the
borkage arises when libffi and gcc belong to different releases.
Is there a simple way to test that the libffi actually works when
compiled, linked, and run? Because then we could implement a TRY_RUN.
The simple test would have to be a valid representation of what's
required to run, though. Otherwise there's no automated way to deduce
that it works, the user would always have to manually specify it.
Cheers,
Brandon Van Every
|