This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Patch: --without-libffi


>>>>> "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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]