[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uclibc-cvs
Subject:    [Bug 305] New: Compilation of udev 137 or higher with uclibc seems to fail because of ppoll() system
From:       bugzilla () busybox ! net (bugzilla at busybox ! net)
Date:       2009-04-24 8:52:45
Message-ID: bug-305-159 () https ! bugs ! busybox ! net/
[Download RAW message or body]

https://bugs.busybox.net/show_bug.cgi?id=305

            Target: i686-pc-linux-uclibc
           Summary: Compilation of udev 137 or higher with uclibc seems to
                    fail because of ppoll() system call
           Product: uClibc
           Version: 0.9.30.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
        AssignedTo: unassigned at uclibc.org
        ReportedBy: mickb at free.fr
                CC: uclibc-cvs at uclibc.org
   Estimated Hours: 0.0


>From version 137, udev makes use of ppoll instead of signal pipes. Since this
change, Udev still compiles correctly over uclibc, but crashes at execution and
returns an error related to ppoll() system call.

This point has been raised deeply in a forum thread, and uclibc is highly
suspected to be the origin of the problem:

http://lists.impactlinux.com/pipermail/firmware-impactlinux.com/2009-April/000166.html

Personally, I confirm that udev 136 compiles and works perfectly, but I
encounter the same symptom with version 137 and higher, on Linux 2.6.28.9.
Cross-compilation toolchain: GCC 4.3.2, binutils 2.19


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[prev in list] [next in list] [prev in thread] [next in thread]