Bugzilla Bug 118062

Microsoft.Win32/UnixRegistryApi.cs(236) error CS1502: The best overloaded match
for method ' System.Threading.Timer..ctor (System.Threading.TimerCallback,
object, uint, uint)' has some invalid arguments
Microsoft.Win32/UnixRegistryApi.cs(236) error CS1503: Argument 3: Cannot
convert from 'int' to 'uint'
Microsoft.Win32/UnixRegistryApi.cs(236) error CS1501: No overload for method
`System.Threading.Timer' takes `4' arguments
Microsoft.Win32/UnixRegistryApi.cs(236) error CS1501: New invocation: Can not
find a constructor in `System.Threading.Timer' for this argument list
Compilation failed: 4 error(s), 0 warnings
make[8]: *** [../../class/lib/basic/mscorlib.dll] Error 1
make[8]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/mcs/class/corlib'
make[7]: *** [do-all] Error 2
make[7]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/mcs/class/corlib'
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/mcs/class'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/mcs'
make[4]: *** [profile-do--basic--all] Error 2
make[4]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/mcs'
make[3]: *** [profiles-do--all] Error 2
make[3]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/mcs'
make[2]: *** [all-local] Error 2
make[2]: Leaving directory
`/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1/runtime'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/mono-1.1.12.1/work/mono-1.1.12.1'
make: *** [all] Error 2

!!! ERROR: dev-lang/mono-1.1.12.1 failed.
!!! Function src_compile, Line 74, Exitcode 2
!!! MONO compilation failure
!!! If you need support, post the topmost build error, NOT this status message.

Can you please post your emerge --info output?

Also, I have a hunch this is the installed mono not being able to compile the
newer mono release, If you have mono installed, can you try removing that, then
trying to install mono again? Thanks.

that worked

Ok, can you check your emerge.log to see what version of mono you'd had
installed that caused the problem, and report it here please? I'd like to add a
check to the mono ebuild so the issue can be caught and reported to the user
appropriately. Thanks.

dev-lang/mono-1.0.5-r5

Any news? Would be great if this bug goes.. I have the axact same problem..
Cannot really update my world now..
Thanks!

Bart: Please see the fact that unmerge the installed mono fixed the problem for
the original poster. Does this fix it for you? Do you really get the *exact*
same error message, or just some problem in general with emerging mono? What is
your emerge --info output? Need more info, thanks.

I followed Peter's advice: removed mono-1.1.7-r1 and emerged mono-1.1.12 again.
It built successfully this way! :)

I just don't understand why!

Here is my emerge info:
Portage 2.0.53 (default-linux/ppc/2004.3, gcc-3.4.4, glibc-2.3.5-r3,
2.6.10-gentoo-r6y ppc)
=================================================================
System uname: 2.6.10-gentoo-r6y ppc 750FX
Gentoo Base System version 1.6.13
ccache version 2.3 [disabled]
dev-lang/python:     2.2.3-r6, 2.3.5, 2.4.2
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.8.1-r4
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CBUILD="powerpc-unknown-linux-gnu"
CFLAGS="-O3 -mcpu=750 -pipe"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config
/usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown
/usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown
/usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref
/usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/X11/app-defaults /etc/gconf /etc/terminfo
/usr/X11R6/lib/X11/xkb /etc/env.d"
CXXFLAGS="-O3 -mcpu=750 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://mir.zyrianes.net/gentoo/ http://gentoo.inode.at/
ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
http://mirror.uni-c.dk/pub/gentoo/"
LINGUAS="it"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="ppc X aac aalib alsa arts audiofile berkdb bitmap-fonts boo bootsplash
browserplugin bzip2 cdparanoia cdr crypt cups curl dbus doc dv dvd dvdr dvi eds
emboss encode esd exif expat fam fbcon ffmpeg firefox flac font-server
foomaticdb fortran gd gdbm gif gimpprint glitz glut gnome gnutls gphoto2 gpm
gstreamer gtk gtk2 gtkhtml hal howl idn ieee1394 imagemagick imlib ipv6 jabber
jack java jpeg junit kde lcms ldap libwww live lua mad mng mono motif mozilla
mp3 mpeg musicbrainz ncurses network nls nptl nsplugin objc ofx ogg oggvorbis
openal opengl oss pam pcre pdflib perl pic png ppds python qt quicktime
rdesktop readline ruby samba scanner sdl slang slp speex spell sqlite ssl
subversion svg t1lib tcpd tetex theora tiff truetype truetype-fonts type1-fonts
udev unicode usb vidix visualization vnc vorbis wifi wmf xine xinerama xml2
xmms xprint xscreensaver xv zeroconf zlib linguas_it userland_GNU kernel_linux
elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, MAKEOPTS

Also on x86.  Same error using mono 1.0.6.  Removing old version and
re-emerging new version works

I noticed in a different bug there was this line in their compile:

-d:BOOTSTRAP_WITH_OLDLIB

I'm not entirely sure, but does mono compile using an existing version if it is
installed?  This might explain why certain people can only upgrade gradually
rather than from a real old version to a new one.  Can anyone confirm this?

Ok, I just tracked down the source of this problem, and the magic build foo to
get mono to always build using the small bundled mcs/corlib versions. Was able
to reproduce the problem beforehand, and confirm the fix solved the problem.
I've just commited the change to both the 1.1.12 and 1.1.13 ebuilds in portage.
Marking this one FIXED, thank god.

Feel free to reopen if you continue to have issues, but i'm confident that at
least this one bug is zapped and dead.