Created attachment 322657 [details] build.log dev-libs/libnl-3.2.12.ebuild introduces $(use_enable doc) that causes a ./configure failure when USE="-doc" is set. I looked into this a bit, and it seems that --disable-doc was introduced upstream in libnl-3.2.10, and it has been broken always. 3.2.9 ./configure --disable-doc: configure: WARNING: unrecognized options: --disable-doc 3.2.10 ./configure --disable-doc: configure: error: conditional "LINK_DOC" was never defined. Usually this means the macro was only invoked conditionally. Anyway, 3.2.12 in portage today currently fails with the same error as 3.2.10. build.log attached, config.log incoming.
Created attachment 322659 [details] config.log
*** Bug 433589 has been marked as a duplicate of this bug. ***
*** Bug 433617 has been marked as a duplicate of this bug. ***
*** Bug 433555 has been marked as a duplicate of this bug. ***
*** Bug 433639 has been marked as a duplicate of this bug. ***
*** Bug 433623 has been marked as a duplicate of this bug. ***
*** Bug 433575 has been marked as a duplicate of this bug. ***
*** Bug 433567 has been marked as a duplicate of this bug. ***
*** Bug 433643 has been marked as a duplicate of this bug. ***
*** Bug 433641 has been marked as a duplicate of this bug. ***
*** Bug 433659 has been marked as a duplicate of this bug. ***
Easiest solution for this is to move those conditionals after "fi" from --disable-docs in configure.in and reexecute autoconf.
*** Bug 433661 has been marked as a duplicate of this bug. ***
*** Bug 433625 has been marked as a duplicate of this bug. ***
*** Bug 433597 has been marked as a duplicate of this bug. ***
Someone on the forums (http://forums.gentoo.org/viewtopic-p-7129184.html) reported the following sequence commands to work, while we have USE flag -doc: sed -i 's/use_enable\ doc/use_disable doc/' /usr/portage/dev-libs/libnl/libnl-3.2.12.ebuild ebuild /usr/portage/dev-libs/libnl/libnl-3.2.12.ebuild digest sudo emerge libnl -1 So, I feel that it's just that the ebuild needs to correctly respond to the USE flag doc. No need to change ./configure at all, as far as I can see.
There is no use_disable. The change needs to be to the configure.
jama libnl-3.2.12 # diff -uNr configure.in.orig configure.in --- configure.in.orig 2012-08-30 13:41:22.000000000 +0200 +++ configure.in 2012-09-01 19:12:44.481322735 +0200 @@ -148,11 +148,12 @@ link_doc=no fi - AM_CONDITIONAL([LINK_DOC], [test "x$link_doc" = "xyes"]) - AM_CONDITIONAL([HAVE_DOXYGEN], [test "x$HAVE_DOXYGEN" = "xyes"]) - AM_CONDITIONAL([HAVE_ASCIIDOC], [test "x$HAVE_ASCIIDOC" = "xyes"]) fi +AM_CONDITIONAL([LINK_DOC], [test "x$link_doc" = "xyes"]) +AM_CONDITIONAL([HAVE_DOXYGEN], [test "x$HAVE_DOXYGEN" = "xyes"]) +AM_CONDITIONAL([HAVE_ASCIIDOC], [test "x$HAVE_ASCIIDOC" = "xyes"]) + AM_CONDITIONAL([GENERATE_DOC], [test "x$generate_doc" != "xno"]) AC_ARG_WITH([pkgconfigdir], AS_HELP_STRING([--with-pkgconfigdir=PATH], $ autoconf and it builds fine
Ah, this is libnl breaking every other minor release.
01 Sep 2012; Jeroen Roovers <jer@gentoo.org> libnl-3.2.12.ebuild, +files/libnl-3.2.12-doc.patch: Fix building with USE=-doc by Ben Kohler (bug #433565), patch by Martin Jansa.
*** Bug 433671 has been marked as a duplicate of this bug. ***
*** Bug 434068 has been marked as a duplicate of this bug. ***
This is fixed upstream and should be OK in 3.2.13.