[Mono-bugs] [Bug 498692] New: many problems cross-building with gcc 4.2.x mingw cross

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=498692


           Summary: many problems cross-building with gcc 4.2.x mingw
                    cross
    Classification: Mono
           Product: Mono: Runtime
           Version: unspecified
          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.0.9)
Gecko/2009042115 Fedora/3.0.9-1.fc10 Firefox/3.0.9

I had a lot of problems with gcc 4.2.x mingw cross (which I used for other
occasions) building mono 2.4 . Then I looked up what the build farm use, and it
is 3.4.5. Seems that gcc 4.2.x is not happy with some of the code when cross
compiling, or when building for windows. I don't know what gcc is available
under cygwin, so I cannot say if the problem is there or not. Rebuilding and
downgrading my cross-compiler to 3.4.5, I managed to cross-build mono 2.4.

Here are a few examples of problems - it is not happy with GC_WIN32_THREADS
being defined both in command line and in code defines. Not happy with FARPROC
in line 479 of libgc/misc.c: 

          (FARPROC) pfn = GetProcAddress(hK32,
               "InitializeCriticalSectionAndSpinCount");

Not happen with the syntax of pointer increment around line 1260 
mono/metadata/image.c:
    ((guint32*) slot)++;

    ((guint64*) slot)++;

I think these were warnings in gcc 3.4.x and becomes errrors in 4.2.1

Reproducible: Always

Steps to Reproduce:
1. try building with gcc 4.2.1 mingw cross.
Actual Results:  
compiler errors.

Expected Results:  
successful compilation.

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