Bugzilla Bug 161410

When trying to emerge gnomevfs-sharp-2.16.0, it fails when running automake.
This is what happens:



* Applying gnome-sharp-2.16.0-configurable.diff ...                      [ ok ]
 * Running eautoreconf in
'/var/tmp/portage/dev-dotnet/gnomevfs-sharp-2.16.0/work/gnome-sharp-2.16.0' ...
 * Requested autoconf 2.5
 * Using autoconf (GNU Autoconf) 2.61
 * Using autoheader (GNU Autoconf) 2.61
 * Requested automake latest: 1.10
 * Using automake (GNU automake) 1.10
 * Using aclocal (GNU automake) 1.10
 * Running aclocal ...                                                    [ ok
]
 * Running libtoolize --copy --force --automake ...                       [ ok
]
 * Running aclocal ...                                                    [ 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/dev-dotnet/gnomevfs-sharp-2.16.0/temp/automake-5423.out


!!! ERROR: dev-dotnet/gnomevfs-sharp-2.16.0 failed.
Call stack:
  ebuild.sh, line 1593:   Called dyn_unpack
  ebuild.sh, line 731:   Called src_unpack
  ebuild.sh, line 1282:   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.

Reproducible: Always

Steps to Reproduce:
1. emerge gnomevfs-sharp

Actual Results:  
gnomevfs-sharp fails to install

Expected Results:  
gnomevfs-sharp should cleanly compile.

This is a pretty severe bug because it prevents basically all serious Mono apps
(Beagle, F-Spot) to be installed!

Created an attachment (id=106450) [details]
Automake failure

Created an attachment (id=106476) [details]
Requested automake output

(From update of attachment 106476 [details])
adam@hotbbq ~ $ emerge --info
Portage 2.1.2_rc4-r7 (default-linux/x86/2006.1/desktop, gcc-4.1.1,
glibc-2.5-r0, 2.6.19-gentoo-r3 i686)
=================================================================
System uname: 2.6.19-gentoo-r3 i686 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.12.8
Last Sync: Wed, 10 Jan 2007 11:50:01 +0000
ccache version 2.4 [enabled]
dev-java/java-config: 1.3.7, 2.0.31
dev-lang/python:     2.4.4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.4-r6
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.19
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=athlon64 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-O2 -march=athlon64 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://open-systems.ufl.edu/mirrors/gentoo"
LC_ALL="en_US.utf8"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://192.168.15.101/gentoo-portage"
USE="3dnow X a52 aac acpi aim alsa apm avahi bash-completion bzip2 cairo caps
cddb cdr cjk cracklib crypt cups dbus dts dvd dvdr dvdread emboss encode exif
fbcon ffmpeg firefox ftp gd gdbm gif glut gnome gnutls gpm gstreamer gtk gtk2
gtkhtml hal imlib ipod java javascript jbig jpeg jpeg2k lcms libcaca mad mikmod
mmap mmx mng mono mp3 mpeg mpi msn ncurses nls nntp nptl nptlonly nsplugin
offensive openal opengl pam pcre pdf perl php png posix ppds profile python
quicktime rdesktop readline samba sdl session sockets spell spl sse sse2 ssl
startup-notification svg svga sysvipc tcpd threads tiff truetype udev unicode
usb win32codecs x86 xml xorg xpm xprint xv xvid zlib" ALSA_CARDS="ali5451
als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938
es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx
via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop
empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi
null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard
mouse" KERNEL="linux" USERLAND="GNU" VIDEO_CARDS="nvidia"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, LINGUAS,
PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

"This is a problem with automake-1.10. get rid of it and all should be well. 

version 1.9.6-r2 of automake seems to work fine (since it's sl;otted it should
still be on your system after you remove 1.10."
I tried masking automake-1.10 and every thing worked fine so that can be a
workaround for now

I recommend a change in the ebuild due to the automake bug.

This package, among other *-sharp packages, compiles fine if automake 
1.9.6 is used. 

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.

> 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.

I was just informed, that "1.9.6" is not a legal value. (Although it compiles
just fine with that line)

You have to change the line given above to:

     WANT_AUTOMAKE="1.9"

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

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

Fixed in bug #161093.

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