>>> Emerging (10 of 102) dev-libs/libpreludedb-1.0.0-r1 * libpreludedb-1.0.0.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking libpreludedb-1.0.0.tar.gz to /var/tmp/portage/dev-libs/libpreludedb-1.0.0-r1/work >>> Source unpacked in /var/tmp/portage/dev-libs/libpreludedb-1.0.0-r1/work >>> Preparing source in /var/tmp/portage/dev-libs/libpreludedb-1.0.0-r1/work/libpreludedb-1.0.0 ... * Applying libpreludedb-1.0.0-ldflags.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/dev-libs/libpreludedb-1.0.0-r1/work/libpreludedb-1.0.0' ... * Running gtkdocize --copy ... [ ok ] * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal -I m4 -I libmissing/m4 ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-libs/libpreludedb-1.0.0-r1/temp/automake.out * ERROR: dev-libs/libpreludedb-1.0.0-r1 failed (prepare phase): * Failed Running automake !
The obvious question is already within the report.
I have found that adding: AM_CONDITIONAL(GTK_DOC_BUILD_HTML, test xyes = xyes) AM_CONDITIONAL(GTK_DOC_BUILD_PDF, test xyes = xyes) to configure.in after the unpack and before configure steps allows it to configure and compile. This is obviously not production, but may hep someone write a correct patch. Now I am just stuck with the install phase
"rm -f m4/gtk-doc-m4" before eautoreconf and adding dev-util/gtk-doc-am to DEPEND was the solution, added to 1.0.0-r1 ebuild
