[Mono-bugs] [Bug 544418] New: Mono build on OSx crashes with Incompatible library version error for libgthread-2.0

[bugzilla_noreply at novell.com]

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


           Summary: Mono build on OSx crashes with Incompatible library
                    version error for libgthread-2.0
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.4.x
          Platform: Other
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: prahaladd at gmail.com
         QAContact: mono-bugs at lists.ximian.com
                CC: prahaladd at gmail.com
          Found By: Third Party Developer/Partner


Description of Problem:

Performing a first time clean build on Mac OSx causes a build failure while
"making" profile=basic all.
The cause of the failure is because of the inability to load
libgthread-2.0.0.dylib due to a version mismatch

Steps to reproduce the problem:
1. Follow the steps described in "Building Mono on OSx" on the official
mono-site

Actual Results:
make PROFILE=basic all
dyld: Library not loaded:
/Library/Frameworks/Mono.framework/Versions/2.4.2.3/lib/libgthread-2.0.0.dylib
  Referenced from: /Library/Frameworks/Mono.framework/Versions/2.4.2.3/bin/mono
  Reason: Incompatible library version: mono requires version 1801.0.0 or
later, but libgthread-2.0.0.dylib provides version 601.0.0
make[6]: *** [build/deps/basic-profile-check.exe] Trace/BPT trap
*** The compiler '/usr/bin/gmcs' doesn't appear to be usable.
*** You need a C# compiler version 2.0 or better installed to build MCS
*** Read INSTALL.txt for information on how to bootstrap a Mono installation.
make[5]: *** [do-profile-check] Error 1
make[4]: *** [profile-do--basic--all] Error 2
make[3]: *** [profiles-do--all] Error 2
make[2]: *** [all-local] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
[mono] ~/mono @ exit
logout

The work around is to then build the corlib source separately from a separate
bash without rerunning configure; we just need to run make with external MCS
set to a working version of mono.

Expected Results:

Build should succeed without any manual interventions

How often does this happen? 

Not sure - happens everytime on my machine

Additional Information:

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