[Mono-bugs] [Bug 564000] New: Mono build fails in mono/mini/driver.c due to old sched_setaffinity() function on RHEL3

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Dec 11 10:34:07 EST 2009



           Summary: Mono build fails in mono/mini/driver.c due to old
                    sched_setaffinity() function on RHEL3
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.6.x
          Platform: x86
        OS/Version: RHEL 3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: matt at mc-c.net
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:
Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15

Building Mono fails because mono/mini/driver.c expects sched_setaffinity() to
take 3 arguments, but on at least the two variants of RHEL3 listed above the
function takes two.  The man page indicates it takes 3, but
/usr/include/sched.h doesn't lie: 

[mcc at slag mono-2.6]$ fgrep -hn sched_setaffinity /usr/include/sched.h
76:extern int sched_setaffinity (__pid_t __pid, __const cpu_set_t *__mask)

Reproducible: Always

Steps to Reproduce:
1. Untar mono-2.6 source
2. Run 'configure' without any arguments
3. Run 'make'

Actual Results:  
The following error message will appear:

driver.c: In function `mono_main':
driver.c:1249: warning: passing arg 2 of `sched_setaffinity' makes pointer from
integer without a cast
driver.c:1249: too many arguments to function `sched_setaffinity'
make[4]: *** [driver.lo] Error 1

Expected Results:  
Build should have succeeded.

Reproduced on:
- Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
- Red Hat Enterprise Linux AS release 3 (Taroon)

Both have glibc-2.3.2-95.33 installed.

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