>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
Gary> But for a project built with `make -j', we still need AM_PROG_CC_C_O Gary> and _LT_COMPILER_C_O to understand each others' locks :-( Seems so. I thought it was not needed because when AM_PROG_CC_C_O decides `compile' is required, it is also used when compiling libtool objects. However perhaps I was wrong, because `compile' does something only for *.o and *.obj files, it is a no-op for *.lo files. Maybe we need to tell AM_PROG_CC_C_O about *.lo files. To makes matter worse, because AM_PROG_CC_C_O horribly overwrites CC, it's not clear to me whether AM_PROG_CC_C_O LT_INIT is equivalent to LT_INIT AM_PROG_CC_C_O It looks like Libtool's `-c -o' check would not give the same answer. I haven't dug all this; I think Ralf W sent some mail about it, but I haven't flushed all my mails yet. I agree it would be better to set down a common lock scheme, although that really should not hold any release. -- Alexandre Duret-Lutz
