Summary: | gnome-base/gnome-vfs-2.16.3-r1 shoud be dependent from automake-1.9.6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | stefan |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED WORKSFORME | ||
Severity: | major | CC: | joerg.rebenstorf |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
stefan
2007-07-05 09:27:05 UTC
It already does depend on it (WANT_AUTOMAKE=1.9). Upgrade your system properly, using --deep. *** Bug 185732 has been marked as a duplicate of this bug. *** I am getting the exact same error when trying to install gnome-vfs-2.24.3 * Running automake --add-missing --copy ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/gnome-base/gnome-vfs-2.24.3/temp/automake.out * ERROR: gnome-base/gnome-vfs-2.24.3 failed: * Failed Running automake ! * * Call stack: emerge --deep gnome-vfs does not help neither doe emerge -uD world. Any hints are welcome! /var/tmp/portage/gnome-base/gnome-vfs-2.24.3/temp/build.log is ^[[A^[[119C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32;01m*^[[0m Running libtoolize --copy --force --install --automake ... ^[[A^[[119C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32;01m*^[[0m Running aclocal ... ^[[A^[[119C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32;01m*^[[0m Running autoconf ... ^[[A^[[119C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32;01m*^[[0m Running autoheader ... ^[[A^[[119C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32;01m*^[[0m Running automake --add-missing --copy ... ^[[A^[[119C ^[[34;01m[ ^[[31;01m!!^[[34;01m ]^[[0m ^[[31;01m*^[[0m Failed Running automake ! ^[[31;01m*^[[0m ^[[31;01m*^[[0m Include in your bugreport the contents of: ^[[31;01m*^[[0m ^[[31;01m*^[[0m /var/tmp/portage/gnome-base/gnome-vfs-2.24.3/temp/automake.out ^[[31;01m*^[[0m ERROR: gnome-base/gnome-vfs-2.24.3 failed: ^[[31;01m*^[[0m Failed Running automake ! ^[[31;01m*^[[0m ^[[31;01m*^[[0m Call stack: ^[[31;01m*^[[0m ebuild.sh, line 48: Called src_unpack ^[[31;01m*^[[0m environment, line 3139: Called eautoreconf ^[[31;01m*^[[0m environment, line 963: Called eautomake ^[[31;01m*^[[0m environment, line 932: Called autotools_run_tool 'automake' '--add-missing' '--copy' ^[[31;01m*^[[0m environment, line 436: Called die ^[[31;01m*^[[0m The specific snippet of code: ^[[31;01m*^[[0m die "Failed Running $1 !"; ^[[31;01m*^[[0m ^[[31;01m*^[[0m If you need support, post the output of 'emerge --info =gnome-base/gnome-vfs-2.24.3', ^[[31;01m*^[[0m the complete build log and the output of 'emerge -pqv =gnome-base/gnome-vfs-2.24.3'. ^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/gnome-base/gnome-vfs-2.24.3/temp/build.log'. ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/gnome-base/gnome-vfs-2.24.3/temp/environment'. ^[[31;01m*^[[0m S: '/var/tmp/portage/gnome-base/gnome-vfs-2.24.3/work/gnome-vfs-2.24.3' emerge -uD gnome-vfs solves the problem |