Cleaning up AC_PROG_CC_C_O semantics (was: Re: [PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.)

[+cc bug-autoconf] Reference: On 01/13/2013 10:06 PM, Nick Bowler wrote: > On 2013-01-13, Stefano Lattarini wrote: >> On 01/13/2013 09:01 PM, Nick Bowler wrote: >>> +dnl Automatically invoke AM_PROG_CC_C_O as necessary. Since AC_PROG_CC i

Re: bug#13378: [PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.

On 01/13/2013 10:06 PM, Nick Bowler wrote: > On 2013-01-13, Stefano Lattarini wrote: > >> Another useful follow-up would be to move the AM_PROG_CC_C_O in a private >> macro (to be expanded in AC_CONFIG_COMMANDS_PRE like you did above), and >> make AM_PROG_CC_C_O a no-op (without runtime deprecatio

Re: [PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.

On 2013-01-13, Stefano Lattarini wrote: > On 01/13/2013 09:01 PM, Nick Bowler wrote: >> +dnl Automatically invoke AM_PROG_CC_C_O as necessary. Since AC_PROG_CC is >> +dnl usually called after AM_INIT_AUTOMAKE, we arrange for the test to be >> +dnl done later by AC_CONFIG_COMMANDS_PRE. > > This wo

[PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.

If subdir-objects is made the default Automake behaviour, packages will need to add AM_PROG_CC_C_O to their configure.ac. Instead of that, let's just make the functionality provided by AM_PROG_CC_C_O mandatory for C projects, and have Automake automatically call it as required. This change should

Re: [PATCH 2/2] Automatically call AM_PROG_CC_C_O as required.

On 01/13/2013 09:01 PM, Nick Bowler wrote: > If subdir-objects is made the default Automake behaviour, packages > will need to add AM_PROG_CC_C_O to their configure.ac. Instead of > that, let's just make the functionality provided by AM_PROG_CC_C_O > mandatory for C projects, and have Automake aut