[Mono-bugs] [Bug 515050] New: [Regression] cross-compiling failed at genmdesc.pl with 'Invalid opcode addps'
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Sun Jun 21 20:11:24 EDT 2009
http://bugzilla.novell.com/show_bug.cgi?id=515050
Summary: [Regression] cross-compiling failed at genmdesc.pl
with 'Invalid opcode addps'
Classification: Mono
Product: Mono: Runtime
Version: 2.4.x
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: misc
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: htl10 at users.sourceforge.net
QAContact: mono-bugs at lists.ximian.com
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1b4)
Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4
I have cross-compiling to win32 mono 2.4.0 (and svn later) working on x86_64
linux a month of two ago; with 2.4.2p2, there is a small change: it fails with:
$ perl ../../../mono/mini/genmdesc.pl __i386__ ../../../mono/mini ../../..
/mono/mini/cpu-x86.md cpu-x86.h x86_desc
Invalid opcode addps at line 410
make: *** [cpu-x86.h] Error 25
I can work around this problem by running the newly cross-compiled win32 PE
genmdesc.exe in wine to generate the x86_desc . genmdesc.pl seems to be a newly
introduced replacement in 2.4.2 to the win32 PE genmdesc.exe (or native linux
genmdesc), which isn't used. I did 2.4.0 by running that step in wine, and can
make 2.4.2 continue by doing that in 2.4.2 as well.
Reproducible: Always
Steps to Reproduce:
1. try cross-compiling on a linux machine that could cross-compile 2.4.0/2.2.0
.
2.
3.
Actual Results:
$perl ../../../mono/mini/genmdesc.pl __i386__ ../../../mono/mini
./../../mono/mini/cpu-x86.md cpu-x86.h x86_desc
Invalid opcode addps at line 410
make: *** [cpu-x86.h] Error 25
Expected Results:
compilation continues.
Executing:
wine genmdesc.exe ../../.. /mono/mini/cpu-x86.md cpu-x86.h x86_desc
(the win32 PE exe newly cross-compiled) work around this problem.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list