Summary: | x11-plugins/wmbiff fails to build with >=automake-1.11.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo Dockapp Team <desktop-dock> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://tinderboxlogs.s3.amazonaws.com/tbamd64.excelsior.flameeyes.eu/x11-plugins%3Awmbiff-0.4.27%3A20120616-180735.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 421465 |
Description
Diego Elio Pettenò (RETIRED)
2012-06-16 14:27:04 UTC
You've forgot build log. OK, double correction: - I fail to notice url (even if it was slightly wrong) - automake.out is missing anyway I'll see to get it again soonish. I've lost the automake.out due to fail-clean so now I'm inlining automake.out when failing a package. OTOH just try and it'll fail. If you don't want to install automake-1.12 just set WANT_AUTOMAKE=1.11 and warn upstream. Updated log with the automake.out ...close, but no. If you'd run 'WANT_AUTOMAKE=1.11 autoreconf -vfi' with >=automake-1.11.2, the result would be similar: scripts/Makefile.am:1: `pkglibdir' is not a legitimate directory for `SCRIPTS' Not *explicitly* listed as an error, still a failure. That's a warning, which won't make it fail, it's designed to be that way (now they warn you before they start getting stuff behind you). Just use WANT_AUTOMAKE=1.11 in the ebuild and send the patch upstream if there is one, otherwise do the former then the latter both in the ebuild, just fix it as it fails right now and there is little reason for it to. (In reply to comment #6) > That's a warning, which won't make it fail, it's designed to be that way > (now they warn you before they start getting stuff behind you). > No, the very next line of the output was: autoreconf-2.69: automake failed with exit status: 1 Just see bug 397477. > Just use WANT_AUTOMAKE=1.11 in the ebuild and send the patch upstream if > there is one, otherwise do the former then the latter both in the ebuild, > just fix it as it fails right now and there is little reason for it to. AFAICT, upstream of this package is long dead. ...though *perhaps* dieing on this warning was not intended in automake 1.11, upstream should know. That is strange, unless it's using -Werror in autoamke itself. Although automake-1.11 went from ignoring, to dying on it to pass through fine... the avahi bug you refer is actually fixed by WANT_AUTOMAKE=1.11 (tested where it failed before). (In reply to comment #9) > the avahi bug you refer is actually fixed by WANT_AUTOMAKE=1.11 > (tested where it failed before). which one: the recent one about mkdir_p or the one I've mentioned in previous comment, that was fixed by avahi-0.6.30-automake-1.11.2.patch ? Gha sorry I mixed the two of them (both open in the browser). fixed in tree |