> Since you are simply patching all the configure files, the question > seems academic unless you switch to properly regenerating all of the > configure files using a fixed libtool.m4.
I am actually proposing to fix libtool.m4 and regenerate the configure scripts (which gives the same result as patching, as expected). > However these are maintained, the libjava configure files still need > to be patched to prevent their associated shared libraries from being > inappropriately linked with -flat_namespace on darwin14 and later. Yes, but I don’t know whether libjava and classpath should be patched in GCC, or whether I should report them to be patched somewhere else (like libgo and zlib, for example). It’s important to do it properly, otherwise codebases diverge and maintance becomes difficult. FX
