ngircd with make http://git.nakidai.ru/ngircd/atom?h=rel-26 2012-09-24T18:45:37+00:00 2012-09-24T18:45:37+00:00 Alexander Barton alex@barton.de 2012-09-24T18:45:37+00:00 urn:sha1:3e22fc32f3941ef839b570043283c53eea37470a 2012-09-24T18:28:02+00:00 Alexander Barton alex@barton.de 2012-09-24T18:28:02+00:00 urn:sha1:8cfb9104419d3c00fbef3fe8639eb04f03d83f3d * automake-am11-am12: autogen.sh: detect automake version format a.b.c and a.b configure.ng: don't require GIT tree to detect version string Include .mailmap file in distribution archives Include all build-system files into distribution archives Change build system to support new and old GNU automake 2012-09-24T12:34:16+00:00 Alexander Barton alex@barton.de 2012-09-24T12:34:16+00:00 urn:sha1:8e1beae4e7e57f5ef74fcc82532162a228e2e831 2012-09-23T16:13:55+00:00 Alexander Barton alex@barton.de 2012-09-23T15:55:48+00:00 urn:sha1:192e304b94f239de13b0f10ca01f6694fe6eea40 Starting with GNU automake 1.12, the "de-ANSI-fication support" has been removed, which ngIRCd used to enable building itself on very old systems. Now the problem is, that using automake >= 1.12 isn't working because of the now unsupported M4 macros. Therefore the solution that this patch implements is to dynamically generate the automake input files with our own ./autogen.sh script: configure.ng => configure.in Makefile.ng => Makefile.am This is quite an ugly approach, but it works and enables us to: 1. use current automake >= 1.12 for development and "private builds", 2. still build distribution archives using automake 1.11.x that have "de-ANSI-fication support" enabled in the generated Makefile's. And if you are using Makefile's generated with a automake version newer than 1.11.x (without "de-ANSI-fication support"), the ./configure script warns you not to use this generated build system to generate distribution archives. Drawback of this patch: you MUST use our autogen.sh script, you can't call the autoconf/automake commands directly any more; but autoreconf should still work ...