This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Patch: --without-libffi
- To: <green at redhat dot com>
- Subject: Re: Patch: --without-libffi
- From: Tom Tromey <tromey at redhat dot com>
- Date: 31 May 2001 11:49:22 -0600
- Cc: <java-patches at gcc dot gnu dot org>
- References: <NEBBKJDPKLNNENPPIHCPKECALHAA.green@redhat.com>
- Reply-To: tromey at redhat dot com
>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:
>> Actually I think it makes sense to do both things: if libffi doesn't
>> work, disable the support in libgcj -- but also disable the support if
>> the user asks for it to be disabled.
Anthony> This is the case with my patch, although you have to
Anthony> explicitly disable libffi support in libjava/configure.host.
Anthony> How would could it check itself? By looking for the
Anthony> existance of a libffi build directory?
I was thinking that since libffi knows when it won't work, maybe
libffi could make a libffi.h that does:
#define LIBFFI_DONT_USE_ME
or something. Then we could test for this in libgcj without
additional configuration.
Tom