http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48407
--- Comment #4 from Ralf Corsepius <corsepiu at gcc dot gnu.org> 2011-04-04 11:40:59 UTC --- (In reply to comment #3) > I have this in my local tree. I recall Ian and I discussing that since > Go and GCJ both need libffi, the logic should be smarter. Joel, as you may have gueess, I also have a similar patch as the one you posted here applied, because otherwise "nothing builds", however this is a different issue. So, let me try to refine my issues: * libgo/configure's --without-libffi, suggests GCC (rsp. libgo) could be built without libffi. This apparently does not apply. libgo (currently) strictly requires libffi. In other words, "--without-libffi" doesn't do what a user who is not deeply intimate with libgo, may think it does. libgo/configure's --without-libffi actually is closer to "--with/without-external-libffi" than to "--with/without-libffi". That said, may-be renaming it could be considered. * GCC's toplevel configure doesn't honor --with/without-libffi (neither in the sense of external-ffi nor in the sense of not using libffi).
