Bugzilla Bug 161518

When compiling art-sharp-2.16.0 the compile fails due to usage of automake
1.10. The relevant output is:

--- snip ---
 * Running automake --add-missing --copy ...                              [ !!
]

 * Failed Running automake !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/art-sharp-2.16.0/temp/automake-8729.out


!!! ERROR: dev-dotnet/art-sharp-2.16.0 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_unpack
  ebuild.sh, line 708:   Called src_unpack
  ebuild.sh, line 1255:   Called gtk-sharp-component_src_unpack
  gtk-sharp-component.eclass, line 144:   Called eautoreconf
  autotools.eclass, line 94:   Called eautomake
  autotools.eclass, line 195:   Called autotools_run_tool 'automake'
'--add-missing' '--copy'
  autotools.eclass, line 256:   Called die

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

--- snip ---

This prevents almost all serious c# projects to be build on the gentoo
platform. The automake step completes without problem, when automake-1.9.6 is
used.

Suggested fix:

The easiest way to force usage of automake-1.9.6 is to edit the ebuild and add:

     WANT_AUTOMAKE="1.9.6"

to it.

You have to run:

     "ebuild <name/of/changed/ebuild> digest" afterwards.

Unfortunately these changes will be lost with the next portage sync. You might
want to create a local overlay to circumvent this problem.

Reproducible: Always

Steps to Reproduce:
1. Compile dev-dotnet/art-sharp-2.16.0


Actual Results:  
The compile fails.

Expected Results:  
Compile is expected to succeed!

(In reply to comment #0)
> The easiest way to force usage of automake-1.9.6 is to edit the ebuild and add:
>      WANT_AUTOMAKE="1.9.6"

Not a legal value; 1.9 is...

Same problem with x86 stable ebuild (2.8.0), and the suggested solution works
fine (as amended by comment #1).

confirmed on x86 and ~x86, both freshly built installations.

Fixed in bug #161093.

*** This bug has been marked as a duplicate of bug 161093 ***

*** Bug 162820 has been marked as a duplicate of this bug. ***