Summary: | kde-base 3.2.0 build error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aaron Day <daya+gentoo> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | nsr2oo2 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aaron Day
2004-02-13 04:25:46 UTC
*** Bug 42017 has been marked as a duplicate of this bug. *** "emerge sync", "emerge autoconf", then "emerge -c" commenting on comment #2: i've tried that, resulting in: >> No outdated packages were found on your system. But I've fixed the autom4te issue by hand: there were leftover files from previous installations of autoconf in /usr/bin, i.e /usr/bin/auto{conf,header,m4te,reconf,scan,update}-x.yz where x.yz all of 2.13, 2.57 and 2.58 - although only autoconf-2.58-r1 is installed. I've [re]moved all leftover binaries and all is working. arch == sparc64 I had the same problem, stale files from 2.57 lying around, belonging to no package. Wonder why that happened... fixed after cleaning out old autoconf versions - more recent versions have this problem fixed. |