Fix libtool.m4 for Darwin >= 10.10

[Jakub Jelinek]

On Tue, Nov 11, 2014 at 03:59:03PM +0100, FX wrote:
> 
> > 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.

libjava is maintained in GCC, libjava/classpath, while imported
occassionally from upstream, would upon merge result in regenerating the
generated files and thus should be patched too.  For the latter,
you should put it into libjava/classpath/ChangeLog.gcj.

	Jakub