./autogen.sh would not work at first saying that autoconf had to be 2.60 or later. So I had to grab and install autoconf-2.63 and m4-1.4.12
I read and understand your explanation but it's what I had to do to get the build going... $ m4 --version m4 (GNU M4) 1.4.12 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by Rene' Seindal. $ autoconf --version autoconf (GNU Autoconf) 2.63 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by David J. MacKenzie and Akim Demaille. Guy Harris wrote: > On Nov 14, 2008, at 5:14 PM, Michael A. McCartney wrote: > >> Michael A. McCartney wrote: >> >> >>> Building on RHL4, upgraded to latest source >>> and now get the following... >>> >>> $ ./autogen.sh >>> Checking for python. >>> aclocal -I ./aclocal-fallback >>> configure.in:1562: file `plugins/Custom.m4' does not exist >>> >> @@ -1559,7 +1559,7 @@ >> dnl Save the cacheable configure results to config.cache before >> recursing >> AC_CACHE_SAVE >> >> -sinclude(plugins/Custom.m4) dnl >> +####sinclude(plugins/Custom.m4) dnl >> > > To quote > > http://www.gnu.org/software/m4/manual/m4.html > > section 9.1: > > If file does not exist, is a directory, or cannot otherwise be read, > the expansion is void, and include will fail with an error while > sinclude is silent. The empty string counts as a file that does not > exist. > > What part of "is silent" does the version of M4 that comes with RHL4 > not understand? What does "m4 --version" print on your RHL4 system? > > (It works on my Mac OS X 10.5.x system, with GNU M4 1.4.6, even > without plugins/Custom.m4; presumably the intent is to allow somebody > to create a Custom.m4 file if they need it for a plugin, and have it > be included if it's present, without *requiring* it to be there.) > _______________________________________________ > Wireshark-dev mailing list > [email protected] > https://wireshark.org/mailman/listinfo/wireshark-dev > > _______________________________________________ Wireshark-dev mailing list [email protected] https://wireshark.org/mailman/listinfo/wireshark-dev
