[Mono-bugs] [Bug 577854] New: Can't compile Mono with the latest trunk

[bugzilla_noreply at novell.com]

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

http://bugzilla.novell.com/show_bug.cgi?id=577854#c0


           Summary: Can't compile Mono with the latest trunk
    Classification: Mono
           Product: Mono: Runtime
           Version: SVN
          Platform: x86
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: a.cailliau at ac-graphic.net
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.6
(KHTML, like Gecko) Chrome/4.0.264.0 Safari/532.6

I can't compile the latest version of Mono from the SVN trunk. I got the
following error at linking:

LD    libmono.la
libs/aot-runtime.o: In function `decode_method_ref':
/home/acailliau/Devel/mono/mono/mono/mini/aot-runtime.c:590: undefined
reference to `mono_gc_get_write_barrier'
/usr/bin/ld: .libs/libmono.so.0.0.0: hidden symbol `mono_gc_get_write_barrier'
isn't defined
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: ld returned 1 exit status
make[4]: *** [libmono.la] Error 1
make[4]: Leaving directory `/home/acailliau/Devel/mono/mono/mono/mini'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/acailliau/Devel/mono/mono/mono/mini'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/acailliau/Devel/mono/mono/mono'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/acailliau/Devel/mono/mono'
make: *** [all] Error 2
zsh: exit 2     make

The bug appears after revision 150992

Reproducible: Always

Steps to Reproduce:
1. Checkout from svn
2. Configure
3. Make



I'd be glad to help, I just need some guidance

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