ngircd with make http://git.nakidai.ru/ngircd/atom?h=rel-22 2013-01-27T11:54:48+00:00 2013-01-27T11:54:48+00:00 Alexander Barton alex@barton.de 2013-01-27T11:54:48+00:00 urn:sha1:c891b5f250c71c1b8f94a002c13db6035ad28305 For example OpenBSD uses a "autoconf" and "automake" wrapper script which tells the user to set AUTOCONF_VERSION and AUTOMAKE_VERSION environment variables. This patch enhances autogen.sh to not detect these wrapper scripts as regular autoconf/automake commands but to set the required environment variables after detecting the real "command-X.Y" commands. Tested on OpenBSD 5.1. 2013-01-27T11:25:58+00:00 Alexander Barton alex@barton.de 2013-01-27T11:25:58+00:00 urn:sha1:419ff38a07cb0b1637b444c96cd6868a7a9e5524 "egrep -o" isn't portable and not available on OpenBSD, for example. So let's use sed instead to get the automake version. The expression used now is less specific but should work as well ... 2013-01-05T02:05:56+00:00 Alexander Barton alex@barton.de 2013-01-05T02:05:56+00:00 urn:sha1:0703fcd71983bd04f70101fd0143660174d22f84 2013-01-05T01:39:06+00:00 Alexander Barton alex@barton.de 2013-01-05T01:37:55+00:00 urn:sha1:4594583f52c46105ffd77eaaf4d9784809567324 2012-09-24T18:40:31+00:00 Alexander Barton alex@barton.de 2012-09-24T18:40:31+00:00 urn:sha1:e65a35e964e6a32de748f18e1f70ffe2ad146119 This fixes automake: warning: autoconf input should be named 'configure.ac', not 'configure.in' when running the autogen.sh script. 2012-09-24T16:01:47+00:00 Alexander Barton alex@barton.de 2012-09-24T16:01:47+00:00 urn:sha1:039a939cb8a85f242a017cb4c68003af2b02dfca 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 ... 2012-09-13T16:25:50+00:00 Alexander Barton alex@barton.de 2012-09-13T16:25:50+00:00 urn:sha1:7eb3932d3a3d6684b4c58c357bab12c2125c1775 2010-10-24T19:51:38+00:00 Alexander Barton alex@barton.de 2010-10-20T22:20:08+00:00 urn:sha1:8288878122468e47df8cc77dfafd5c558508bbec Now the ngIRCd release/version number is deduced from the "current" annotated GIT tag; see "git describe --help" for details. This is the same scheme the Linux kernel uses and gives much more details version numbers for interim releases and inofficial source archives generated using "make dist". Please note: the version number is only updated it the autogen.sh script is run; so after pulling in and pushing out new commits, you should run ./autogen.sh! 2008-06-27T03:55:45+00:00 Alexander Barton alex@barton.de 2008-06-27T03:55:45+00:00 urn:sha1:da160d020ee2c2911a0d2ad2fd1074e8971db0ad On some systems (for example Gentoo Linux, FreeBSD, and OpenBSD), these variables are used to select which version of GNU automake and autoconf to use, but we shouldn't depend on a specific version -- instead we should use the "system default". So probably it is up to the user to set these variables accordingly to set up some wrapper scripts of his operating system distribution.