[Mono-bugs] [Bug 500999] New: Minimal Build Failure

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue May 5 10:03:07 EDT 2009


           Summary: Minimal Build Failure
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: i686
        OS/Version: Ubuntu
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Configuration
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: amafabee at hotmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Customer

Description of Problem:

Build does not complete as expected when certain flags are applied.

Steps to reproduce the problem:
1. Obtain Mono 2.4 Source and extract to a given directory
2. Navigate to directory
3. Build using "./configure
--enable-nls=no --disable-shared-memory --prefix=/usr/local"
4. Run "make"

Actual Results:
make[4]: Entering directory `/var/tmp/mono-2.4/mono/mini'
LD    libmono.la
libs/mini.o: In function `mini_init':
mini.c:(.text+0x1782): undefined reference to `mono_xdebug_init'
/usr/bin/ld: .libs/libmono.so.0.0.0: hidden symbol `mono_xdebug_init' isn't
/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 `/var/tmp/mono-2.4/mono/mini'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/var/tmp/mono-2.4/mono/mini'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/mono-2.4/mono'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/mono-2.4'
make: *** [all] Error 2

Expected Results:
Successful small-size build

How often does this happen? 
Every time build is attempted

Additional Information:
May be related to absence of gettext, but debug is disabled in the
--enable-minimal section, so why would it fail trying to compile

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