emerge of dev-haskell fails due to (apparently) automake not liking libbuddha/Makefile.am. I think the results below show the problem well. Reproducible: Always Steps to Reproduce: 1. emerge dev-haskell/buddha on amd64 2. 3. Actual Results: >>> Compiling source in /var/tmp/portage/buddha-1.2-r1/work/buddha-1.2 ... * Running eautoreconf in '/var/tmp/portage/buddha-1.2-r1/work/buddha-1.2' ... * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running automake --add-missing --copy ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/buddha-1.2-r1/temp/automake-21478.out !!! ERROR: dev-haskell/buddha-1.2-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile buddha-1.2-r1.ebuild, line 32: Called eautoreconf autotools.eclass, line 98: Called eautomake autotools.eclass, line 195: Called autotools_run_tool 'automake' '--add-missing' '--copy' autotools.eclass, line 219: Called die !!! Failed Running automake ! !!! If you need support, post the topmost build error, and the call stack if relevant. # cat /var/tmp/portage/buddha-1.2-r1/temp/automake-21478.out ***** automake ***** configure.ac:12: AC_CONFIG_AUX_DIR must be called before AM_INIT_AUTOMAKE... configure.ac:6: ... AM_INIT_AUTOMAKE called here data/Makefile.am:31: `:='-style assignments are not portable data/Makefile.am:31: shell pwd: non-POSIX variable name data/Makefile.am:31: (probably a GNU make extension) libbuddha/Makefile.am: installing `config/depcomp' libbuddha/Makefile.am:59: `CFLAGS' is a user variable, you should not override it; libbuddha/Makefile.am:59: use `AM_CFLAGS' instead. Expected Results: Successful build and install. The package is marked ~amd64. There is no stable version of this package marked stable for amd64.
Buddha is bitrotted. I talked to upstream and they agreed. I am p.masking it and will remove it from the portage tree in 30 days.
The package has been removed from portage.
