This bug is used to track packages which fail to build with Autoconf 2.66.
I ask for 2.66 to be written off as broken: AC_CHECK_SIZEOF([void*]) no longer works (see bug #326931)...
Looks like upstream is aware of this regression: http://osdir.com/ml/autoconf-gnu/2010-07/msg00004.html (patch included)
there are others too, so dont use autoconf-2.66 yet
2.66 has been punted from the tree and 2.67 is in now if people want to stress that version
just got this bug http://thread.gmane.org/gmane.comp.sysutils.autoconf.general/13133/focus=13153 while configuring libgphoto2-2.4.9 with autoconf-2.67
hm. i'm wrong a bit. error by link above is not exactly the same but very similar. # cat /var/tmp/portage/media-libs/libgphoto2-2.4.9/temp/autoconf.out ***** autoconf ***** ***** PWD: /var/tmp/portage/media-libs/libgphoto2-2.4.9/work/libgphoto2-2.4.9/libgphoto2_port ***** autoconf configure:11176: error: possibly undefined macro: AS_MESSAGE_LOG_FDdnl If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
I assume autoconf-2.68 is the next stable target. It fixes a lof of 2.66 and 2.67 regressions. - pkg-config, libgphoto2, luatex were broken and have been fixed - some dotnet packages fail with 2.66 and 2.67 but succeed with 2.65 and 2.68, therefore not a issue... works with latest stable, and latest ~arch So no bugs left, closing