Bugzilla Bug 17614

When trying to emerge mono-0.23, upgrading from mono-0.20, I get the error 
message stating that mono and corlib are out of sync. I then tried emerging 
mono-0.22, which succeeded, and retrying mono-0.23 after that succeeds as well.

Reproducible: Didn't try
Steps to Reproduce:
1. Emerge mono-0.20
2. Emerge mono-0.23
Actual Results:  
Emerging mono-0.23 complains about mono and corlib being out of sync.


# emerge info
Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2)
=================================================================
System uname: 2.4.20-gentoo-r1 i686 Celeron (Mendocino)
GENTOO_MIRRORS=" http://gentoo.linux.no/ ftp://gentoo.linux.no/pub/gentoo/ 
http://212.219.56.146/sites/www.ibiblio.org/gentoo/ 
http://194.83.57.3/sites/www.ibiblio.org/gentoo/ 
http://ftp.easynet.nl/mirror/gentoo// ftp://ftp.easynet.nl/mirror/gentoo// 
http://194.83.57.11/sites/www.ibiblio.org/gentoo/ 
http://194.83.57.7/sites/www.ibiblio.org/gentoo/ 
http://194.83.57.2/sites/www.ibiblio.org/gentoo/ ftp://ftp.tu-
clausthal.de/pub/linux/gentoo/"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/shar
e/config /usr/X11R6/lib/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss apm avi crypt cups encode gif gpm java jpeg libg++ mmx mpeg 
ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib berkdb slang 
readline svga tcltk guile X sdl tcpd pam libwww ssl perl python esd imlib 
gnome gtk qt opengl -3dnow -alsa arts doc gd gdbm imap -kde -mikmod -motif -
oggvorbis samba"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=pentium2 -O3 -pipe"
CXXFLAGS="-march=pentium2 -O3 -pipe"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

did it really fail ? i see the message, but it doesnt bomb out or anything and
it still installs the right stuff.

Hmm, I had to try rebuilding it (emerging 0.20, then 0.23), and yes, the emerge
eventually completes. I guess those messages were nasty enough to make the
ebuild look broken, and in any event, I would have an uneasy feeling about
using that particular version of mono after such pesky warnings. But if you
think the build is okay, I'm sufficiently reassured.

I've seen the same thing while trying to upgrade from mono-0.19 to mono-0.2x,
including mono-0.23. Unmerging mono (which removes corlib), then emerging mono
solved the problem.

It might be a problem with the link order (ie /usr/lib/corlib.dll is used
instead of the build corlib.dll), but I haven't really researched it.

ok, i did some fixes in the new 0.24 ebuild that should take care of this.