>>> Emerging (5 of 14) app-editors/xemacs-21.5.28-r2 to / * NeXT_XEmacs.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * xemacs-21.5.28.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking xemacs-21.5.28.tar.gz ;-) ... [ ok ] * checking NeXT_XEmacs.tar.gz ;-) ... [ ok ] >>> cfg-update-1.8.2-r1: Skipping checksum index updating... >>> Unpacking source... >>> Unpacking xemacs-21.5.28.tar.gz to /var/tmp/portage/portage/app-editors/xemacs-21.5.28-r2/work * Applying gdbm-and-db.patch ... [ ok ] * Applying font-lock-warning-face.patch ... [ ok ] * Applying xemacs-21.5.28-int-format.patch ... [ ok ] * Applying xemacs-21.5.28-vcdiff.patch ... [ ok ] * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/portage/app-editors/xemacs-21.5.28-r2/temp/autoconf-21388.out * * ERROR: app-editors/xemacs-21.5.28-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3028: Called eautoconf * environment, line 941: Called autotools_run_tool 'autoconf' * environment, line 471: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running autoconf ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/portage/app-editors/xemacs-21.5.28-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/portage/app-editors/xemacs-21.5.28-r2/temp/environment'. * ############################################## ***** autoconf ***** ***** autoconf configure.ac:392: error: possibly undefined macro: m4_fst If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. Reproducible: Always
builds fine with autoconf-2.61-r1
fails again with autoconf-2.62 with the same error
This works fine with the xemacs-21.5.28 ebuild I just committed to Portage this morning: : jmglov@laurana; equery list autoconf [ Searching for package 'autoconf' in all categories among: ] * installed packages [I--] [ ] sys-devel/autoconf-2.13 (2.1) [I--] [ ] sys-devel/autoconf-2.61-r1 (2.5) [I--] [ ] sys-devel/autoconf-wrapper-4-r3 (0) : jmglov@laurana; equery list app-editors/xemacs [ Searching for package 'xemacs' in 'app-editors' among: ] * installed packages [I--] [M~] app-editors/xemacs-21.5.28 (0) Will you please try to repro this bug with 21.5.28? Also, where did the ebuild referenced in this bug come from?
I've package.mask'ed this version just now: it it broken and it contains security violations. Obviously your version does not have the problem Jochen reported since you don't need to patch the configure script to fix problems and thus run eautoconf. Current work is going on in the xemacs overlay: layman -a xemacs.
This is reported upstream as http://tracker.xemacs.org/XEmacs/its/issue370
I've applied a patch from upstream to xemacs-21.5.28-r4 in the xemacs overlay, and it should now work with autoconf 2.61 and 2.62. The fix is present in r1112. I'm still using 2.61 myself, so I would appreciate feedback on whether this is actually fixed with 2.62. Please re-open the bug if there are still issues.
