b) patch glib2-2.30 to make libffi optional (and then maintain patches)Actually I would prefer that solution (and use it everywhere). Glib2 needing a dynamic foreign call interface scares me.Unfortunately... glib2 uses it to implement its generic closure support (g_cclosure_marshal_generic), which seems to be pretty pervasive. I think maintaining a glib 2.28 is probably going to be the most practical option at this point...
What's the biggest hurdle in VAX libffi? John