Summary: | x11-libs/libXt-1.0.5 problems with WANT_AUTOMAKE | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | Eclasses | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 360404, juliandimitrov, orionbelt2 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 226305 |
Description
Diego Elio Pettenò (RETIRED)
2009-05-15 23:57:45 UTC
*** Bug 270019 has been marked as a duplicate of this bug. *** *** Bug 270197 has been marked as a duplicate of this bug. *** I've added WANT_AUTOMAKE="1.9" to the ebuild without a revbump. That ought to fix it... Thanks You *did* confirm it doesn't work with 1.10 didn't you? Well... that's what this bug was about, wasn't it? Uh, no, the bug was with some bad interaction (afaics) between x-modular and autotools eclasses... Problem seems to have reappeared. I was updating world today, which pulled in net-nds/openldap-2.4.24 , which failed to run aclocal in the prepare phase: * Running aclocal ... [ !! ] * Failed Running aclocal ! * * Include in your bugreport the contents of: * * /var/tmp/portage/net-nds/openldap-2.4.24/temp/aclocal.out * ERROR: net-nds/openldap-2.4.24 failed (prepare phase): * Failed Running aclocal ! % cat /var/tmp/portage/net-nds/openldap-2.4.24/temp/aclocal.out ***** aclocal ***** ***** PWD: /var/tmp/portage/net-nds/openldap-2.4.24/work/openldap-2.4.24 ***** aclocal am-wrapper: warning: invalid WANT_AUTOMAKE 'none'; ignoring. am-wrapper: /usr/bin/aclocal-1.9 is missing or not executable. Please try emerging the correct version of automake. % equery list automake * Searching for automake ... [IP-] [ ] sys-devel/automake-1.11.1:1.11 Why require automake-1.9 when automake-1.11 is the current version? Is 1.9 really needed? A few days after i submitted my comment, automake-1.9 was reinstalled in a separate SLOT from 1.11, and the problem disappeared. I suppose it was discussed and fixed in some other bug thread ;) |