[Bug 45064] New: building wine-mono 4.7.1 fails with " out of sync mscorlib.dll" on debian 9 stretch 64-bit
https://bugs.winehq.org/show_bug.cgi?id=45064 Bug ID: 45064 Summary: building wine-mono 4.7.1 fails with "out of sync mscorlib.dll" on debian 9 stretch 64-bit Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 61201 --> https://bugs.winehq.org/attachment.cgi?id=61201 full wine-mono build log I'm trying to build wine-mono myself so that I can start fixing bugs in mono that are triggered by some windows native .NET apps. Here's the steps I've followed: - Install Debian 9 stretch 64 bits in a virtualbox 5.2.10 virtual machine with guest additions (3.9GB RAM, 3.40Ghz x6 CPU); - full package update; - Install wine-3.6 WoW64 unpatched custom build in /home/wine-tools/wine-builds/3.6_plain_wow (same prefix as make install). - Install package git 1:2.11.0-3+deb9u2 (+all dependencies); - add i386 architecture to dpkg; - Install package libc6-i386 2.24-11+deb9u3; - Install package mono-mcs 4.6.2.7+dfsg-1 (+all dependencies); - Install packages autoconf 2.69-10 & automake 1:1.15-6 (+all dependencies); - Install package libtool 2.4.6-2 (+dependency); - Install package mingw-w64 5.0.1-1 (+dependency); - Install package g++ 4:6.3.0-4 (+all dependencies); - Install package cmake 3.7.2-1 (+all dependencies); - Install package gettext 0.19.8.1-2; - Install packages build-essential 12.3 & mono-devel 4.6.2.7+dfsg-1 (+all dependencies); - Ran $ git clone --recursive git://github.com/madewokherd/wine-mono.git - cd in build dir (/home/olivier/src/wine-mono; git clone created the wine-mono part) - Ran $ git checkout wine-mono-4.7.1 - Ran $ git submodule update --recursive - Ran $ WINE=/home/wine-tools/wine-builds/3.6_plain_wow/bin/wine64 ./build-winemono.sh >~/tmp/wine-mono.log.txt 2>&1 --- log --- (...) if test -w /home/olivier/src/wine-mono/mono/mcs; then :; else chmod -R +w /home/olivier/src/wine-mono/mono/mcs; fi cd /home/olivier/src/wine-mono/mono/mcs && make --no-print-directory -s NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14 ' CC='gcc' all-profiles cant resolve internal call to "System.RuntimeTypeHandle::HasReferences(System.RuntimeType)" (tested without signature also) Microsoft (R) Visual C# Compiler version 2.0.0.61404 Copyright (C) Microsoft Corporation. All rights reserved. Your mono runtime and class libraries are out of sync. The out of sync library is: /media/wine-shares/mono/mono/mcs/class/lib/monolite/mscorlib.dll When you update one from git you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. CSC [basic] mscorlib.dll cant resolve internal call to "System.RuntimeTypeHandle::HasReferences(System.RuntimeType)" (tested without signature also) (...) --- end --- It's not clear what the build script is doing at that point and so not clear which mono runtime the error is about or where the offending class libraries came from. How can I fix that so that I can build wine-mono? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 --- Comment #1 from Vincent Povirk <madewokherd(a)gmail.com> --- The Mono build system will download monolite if it cannot use the system's Mono. Since you are building from a branch, I recommend using the monolite folder from a source tarball. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Vincent Povirk from comment #1)
Since you are building from a branch, I recommend using the monolite folder from a source tarball.
I copied the ./monolite folder from wine-mono-4.7.1.tar.gz over to the wine-mono GIT tree at the same level as in the tarball and the same error occurred. The monolite folder contains mcs.exe and a bunch of *.dll. How do I use it? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 --- Comment #3 from Vincent Povirk <madewokherd(a)gmail.com> --- It should be picked up automatically by the build script. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #4 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Vincent Povirk from comment #3)
It should be picked up automatically by the build script.
It did not pick up the monolite folder until I restarted from scratch, otherwise it kept using the downloaded monolite and throw 'out of sync' errors. After that, there were other dependency errors so I gave up building from GIT. I build from the source tarball instead and it works. The out of sync error is caused by the mono build system downloading a monolite version that is not in sync with the branch, so I'll resolve it NOTOURBUG. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 --- Comment #5 from Vincent Povirk <madewokherd(a)gmail.com> --- Well, that depends on whether the problem has anything to do with our using a modified version of Mono. I don't think it should, but I won't be able to investigate. This is why the source tarballs have monolite - they need to be self-contained and not rely on Mono's build server. Hopefully the master branch works better. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45064 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED --- Comment #7 from Austin English <austinenglish(a)gmail.com> --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream. Setting back to RESOLVED NOTOURBUG. Sorry for the spam. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org