Anthony Green <[EMAIL PROTECTED]> writes:
> > Hmm... maybe we should just stop packaging libffi up with japhar.
>
> Nobody has reported any libffi problems to me. What's going on?
There's some type of problem with the libffi build process inside of
Japhar's CVS tree -- libffi builds, but ffi_call doesn't end up in the
resulting library. I haven't checked to see if the problem exists
under Japhar 0.08. The `official' libffi 1.20 builds and works fine
for me.
I'll have more time to look into things later in the week.
