Bugzilla Bug 154975

gnome-base/gnome-vfs-2.16.2 does not depend on the correct version of automake.

>>> Unpacking source...
>>> Unpacking gnome-vfs-2.16.2.tar.bz2 to /var/tmp/portage/gnome-base/gnome-vfs-2.16.2/work
 * Fixing OMF Makefiles ...                                                    
                                [ ok ]
 * Applying gnome-vfs-2.12.0-afs.patch ...                                     
                                [ ok ]
 * Applying gnome-vfs-2.15.2-headers-define.patch ...                          
                                [ ok ]
 * Applying gnome-vfs-2.16.0-no-dbus-crash.patch ...                           
                                [ ok ]
 * Running eautoreconf in
'/var/tmp/portage/gnome-base/gnome-vfs-2.16.2/work/gnome-vfs-2.16.2' ...
 * Running aclocal -I . ...                                                    
                                [ !! ]

 * Failed Running aclocal !
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/gnome-base/gnome-vfs-2.16.2/temp/aclocal-13933.out


!!! ERROR: gnome-base/gnome-vfs-2.16.2 failed.
Call stack:
  ebuild.sh, line 1568:   Called dyn_unpack
  ebuild.sh, line 708:   Called src_unpack
  gnome-vfs-2.16.2.ebuild, line 89:   Called eautoreconf
  autotools.eclass, line 83:   Called eaclocal
  autotools.eclass, line 121:   Called autotools_run_tool 'aclocal' '-I' '.'
  autotools.eclass, line 242:   Called die

!!! Failed Running aclocal !
!!! If you need support, post the topmost build error, and the call stack if
relevant.

gauss ~ # cat
/var/tmp/portage/gnome-base/gnome-vfs-2.16.2/temp/aclocal-13933.out
***** aclocal *****

am-wrapper: /usr/bin/aclocal-1.9 is missing or not executable.
            Please try emerging the correct version of automake.



Adding
WANT_AUTOCONF="latest"
WANT_AUTOMAKE="latest"
lets the ebuild die at automake

 * Running aclocal -I . ...                                                    
                                [ ok ]
 * Running autoconf ...                                                        
                                [ ok ]
 * Running autoheader ...                                                      
                                [ ok ]
 * Running automake --add-missing --copy ...                                   
                                [ !! ]

 * Failed Running automake !
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/gnome-base/gnome-vfs-2.16.2/temp/automake-21605.out


!!! ERROR: gnome-base/gnome-vfs-2.16.2 failed.
Call stack:
  ebuild.sh, line 1568:   Called dyn_unpack
  ebuild.sh, line 708:   Called src_unpack
  gnome-vfs-2.16.2.ebuild, line 92:   Called eautoreconf
  autotools.eclass, line 87:   Called eautomake
  autotools.eclass, line 188:   Called autotools_run_tool 'automake'
'--add-missing' '--copy'
  autotools.eclass, line 242:   Called die

!!! Failed Running automake !
!!! If you need support, post the topmost build error, and the call stack if
relevant.

gauss ~ # cat
/var/tmp/portage/gnome-base/gnome-vfs-2.16.2/temp/automake-21605.out
***** automake *****

configure.in:37: version mismatch.  This is Automake 1.10,
configure.in:37: but the definition used by this AM_INIT_AUTOMAKE
configure.in:37: comes from Automake 1.9.6.  You should recreate
configure.in:37: aclocal.m4 with aclocal and run automake again.
daemon/Makefile.am:43: `%'-style pattern rules are a GNU make extension

This will make it work:
WANT_AUTOCONF="latest"
WANT_AUTOMAKE="1.9"

Added.

Works here.
A small cleanup propose: Remove the "=sys-devel/automake-1.9*" from DEPEND, as
that is automatically added by autotools.eclass.

(In reply to comment #2)
> Works here.
> A small cleanup propose: Remove the "=sys-devel/automake-1.9*" from DEPEND, as
> that is automatically added by autotools.eclass.
> 

I have changed it to be WANT_AUTOMAKE=1.9 prior to inheriting autotools.
This makes the automake DEPEND come from autotools, but more importantly it
ensures eautoreconf actually uses 1.9 not, for example, 1.10