Summary: | x11-themes/gnome-icon-theme-3.2.1.2 - configure.ac:8: version mismatch. This is Automake 1.11.6, but the definition used by this AM_INIT_AUTOMAKE comes from Automake 1.11.1. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lsching17 |
Component: | [OLD] GNOME | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | gnome |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
lsching17
2012-08-22 23:19:57 UTC
I can't reproduce this. Shouldn't be happening unless you tried to update sys-devel/automake in the middle of emerging gnome-icon-theme, or unless you had confused automake into thinking that it's running in a source tree with nested configures. Do you have any gnu autotools files (e.g. aclocal.m4, configure.ac, configure.in, Makefile.am, etc.) in one of the directories leading to /custom/tmp/portage/tmp/portage/x11-themes/gnome-icon-theme-3.2.1.2/work/gnome-icon-theme-3.2.1.2 - e.g. in /custom, or /custom/tmp, or /custom/tmp/portage, etc.? This might happen if you, for example, had manually unpacked a source tarball of some package directly in /custom/tmp. my /custom/tmp is on tmpfs, it wiped out on every reboot. Therefore, there should be no non-portage file. $ mount | grep /custom/tmp tmpfs on /custom/tmp type tmpfs (rw,noatime,size=95%,mode=1755) i reboot my PC and perform the following: sudo emerge-webrsync sudo emerge --update --newuse --deep --oneshot x11-themes/gnome-icon-theme same error still occurs. My automake upgrade from 1.11.1 to 1.11.6 recently, is it possible that "unclean" upgrade cause this? Are you able to reproduce this on an updated system? The problem still exist i reboot and update the portage of my PC. The same error still exists. i workaround by downgrading automake to 1.11.1 temporary before emerge This looks like bug 419933, but won't mark as duplicate yet until automake maintainers look at this *** This bug has been marked as a duplicate of bug 419933 *** |