This is the mail archive of the
mailing list for the GCC project.
Re: libffi package
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Thomas Heller <theller at python dot net>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 19 Jan 2004 22:50:17 -0500 (EST)
- Subject: Re: libffi package
I didn't see an answer to this question, so I'll give it a shot. Though I
don't speak for libffi maintainers:
On Fri, 16 Jan 2004, Thomas Heller wrote:
> Are there chances that patches to libffi to compile it with the
> Microsoft compiler for Windows be accepted? Patches for windows
> specific features?
I don't know. The upstream package might, but as this libffi is part of
GCC there is little reason it seems to support other compilers.
What is preventing MSVC from compiling libffi? Inline asm perhaps?
> Are there any ideas to provide libffi as a standalone package, separate
> from GCC, again? Would there by anything I could help to make this
Have you seen the note atop http://sources.redhat.com/libffi/? I suggest
you contact Anthony Green.
> What about the docs? They haven't changed in a few years (that's my
> impression at least).
I'm sure documentation patches would be welcome.
> And finally (IANAL): is the redhat license still the one which applies
> to libffi?
Last I heard, Anthony was trying to reassign the copyright of libffi to
the FSF. For now the Red Hat license is in effect.