The latest version of festival-gaim, 1.1-r1, fails when trying to build against gaim-2.0.0_beta5-r3. I've built the latest versions of gaim-otr, gaim-extprefs, gaim-encryption, and guifications, so that isn't the problem. When I emerge festival gaim, everything seems to be working up to the following error message: make[2]: Entering directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/po' make[2]: Entering directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1' make[1]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1' >>> Source compiled. >>> Test phase [not enabled]: app-accessibility/festival-gaim-1.1-r1 >>> Install festival-gaim-1.1-r1 into /var/tmp/portage/festival-gaim-1.1-r1/image/ category app-accessibility make install-recursive make[1]: Entering directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1' Making install in src make[2]: Entering directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/src' make[3]: Entering directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/src' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/gaim" || /bin/mkdir -p "/var/tmp/portage/festival-gaim-1.1-r1/image//usr/lib/gaim" /bin/sh ../libtool --silent --mode=install /bin/install -c 'festival.la' '/var/tmp/portage/festival-gaim-1.1-r1/image//usr/lib/gaim/festival.la' libtool: install: warning: remember to run `libtool --finish /usr/lib/gaim' make[3]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/src' make[2]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/src' Making install in po make[2]: Entering directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/po' if test -r ".././mkinstalldirs"; then \ .././mkinstalldirs /var/tmp/portage/festival-gaim-1.1-r1/image//usr/share; \ else \ /bin/sh ../mkinstalldirs /var/tmp/portage/festival-gaim-1.1-r1/image//usr/share; \ fi /bin/sh: ../mkinstalldirs: No such file or directory make[2]: *** [install-data-yes] Error 127 make[2]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1/po' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/festival-gaim-1.1-r1/work/festival-gaim-1.1' make: *** [install] Error 2 !!! ERROR: app-accessibility/festival-gaim-1.1-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_install ebuild.sh, line 1020: Called src_install festival-gaim-1.1-r1.ebuild, line 34: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. As you can see, it finishes the compile, saying ">>> Source compiled.", and gets through the non-existent test phase. During the install phase, however, some directory is not found and the whole thing fails. I don't know what's going on here; is there potentially a problem at my end, or is this version of festival-gaim not capable of building against the most recent version of gaim? The only big change 2.0.0_beta5-r3 seems to have brought to gaim was moving to the new dbus-1.0.2; maybe that's related. Reproducible: Always Steps to Reproduce: 1. Upgrade gaim to 2.0.0_beta5-r3, including upgrading dbus 2. Emerge dbus-qt3-old, dbus-python, and dbus-glib, as recommended here: http://www.gentoo.org/news/en/gwn/20061211-newsletter.xml 3. Emerge festival and festival-gaim 4. Receive error message as above Actual Results: Error message and failure of festival-gaim to emerge. Expected Results: Festival-gaim should emerge properly.
The same problem occurs with net-im/gaim-2.0.0_beta6; basically the same error as before (vdiff finds no changes, but I'm not going to bother reposting the whole thing unless someone asks, since I think they're identical). Figured this should be noted.
*** Bug 163463 has been marked as a duplicate of this bug. ***
flameeyes wrongly removed the req on automake 1.7. Its now back and compiles like a charm!
