bug#31347: AM_PROG_CC_C_O is disabled by gnulib std-gnu11.m4

On 03 May 2018 10:11, Jamal Natour wrote: > As a user of C++11 and C++14, I use the ax_cxx_compile_stdcxx variants, > these have seemed to work on the various combinations of > platforms/compilers I've used. > > https://github.com/jamal-fuma/fuma_m4/blob/master/ax_cxx_compile_stdcxx.m4 > https://g

bug#31728: Automake and AM_WITH_DMALLOC; endorsing proprietary software?

confirm 31728 severity 31728 wishlist On 05 Jun 2018 15:09, Nick Bowler wrote: > The trouble is that dmalloc appears to be non-free: the license does > not seem to permit distribution for a fee (see below). first this part. ianal, so i won't try to interpret the nuance here, but it seems a bit m

bug#21336: [PATCH] configure: handle KCC on case-insensitive filesystems

This fixes https://debbugs.gnu.org/21336. On macOS 10.10, there seems to be a kerberos tool installed as "kcc" which breaks the check. Also resync with latest autoconf which searches for clang++ too. * configure.ac: Skip KCC check on case-insensitive filesystems. Add clang++ to the C++ search l

bug#10828: [RFC] POSIX will say running "rm -f" with no argument is OK

On 03 Jan 2013 20:14, Stefano Lattarini wrote: > Reference: > > > [This is posted also to the automake list to ensure a wider audience. > Discussion should continue exclusively on the bug-automake list] > > OK, time to resurrect this thread. >

bug#33711: configure --host=aarch64 produces x86-64 binary

reassign 33711 autoconf thanks On 11 Dec 2018 22:07, Erik van Velzen wrote: > I compiled https://github.com/json-c/json-c using the command `sh > autogen.sh && ./configure --host=aarch64 && make`. Unexpectedly this > creates an x64 binary. > > The correct argument in my case is --host=aarch64-lin