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
On 2013-01-12 11:05 +0100, Stefano Lattarini wrote:
On 01/11/2013 08:16 PM, Stefano Lattarini wrote:
On 01/11/2013 07:19 PM, Eric Blake wrote:
On 01/10/2013 06:33 AM, Stefano Lattarini wrote:
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#50
@acindex AC_PROG_CC_C_O
If AM_PROG_CC_C_O is expanded multiple times, and the compiler does not
support -c and -o together, each expansion of the macro will prepend
the compile script to CC. This can result in the compile script
invoking the compile script, which at best pointless and silly.
Fortunately, there does not
On 2013-01-13, Stefano Lattarini stefano.lattar...@gmail.com 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
On 01/12/2013 04:45 AM, Stefano Lattarini wrote:
As a rule of thumb on when to remove a macro - I would personally like
being able to write a configure script that works on both RHEL 5 (or
CentOS 5) (autoconf 2.59, automake 1.9.6) as well as rawhide (eventually
automake 1.14 and beyond),
