[systemd-bugs] [Bug 73729] udev fails to build with uclibc

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=73729

Nico Nelson <nico.nelson-91c8b80 at yopmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #12 from Nico Nelson <nico.nelson-91c8b80 at yopmail.com> ---
(In reply to comment #11)
> (In reply to comment #9)
> > (In reply to comment #7)
> > > We are certainly not rvereting the %m work. 
> > 
> > using the term "work" for that seems to a bit bold.
> > 
> > > We make use of glibc and gcc
> > > extensions where they make sense. 
> > 
> > it certainly didn't make sense here. the existing code did exactly the same
> > thing, but in a manner guarantueed to work by both C and POSIX standards.
> 
> udev and systemd are Linux specific. We program against the Linux platform,
> not against POSIX. 

the Linux platform comprises of more than just glibc, so you have to stick to
POSIX plus linux specific syscalls and structs.

relying on stuff such as glibc's %m feature could be considered as an
intentional act of sabotage against other libc implementations to create a
modern linux apartheid where you can use a desktop environment only if you use
redhat financed projects with all their dependencies. and that's what just
happening right now, as udev dependencies have crept into the X11 stack
(xf86-input-evdev), udev itself crept into systemd, which deliberately uses
glibc specifics to keep the competition out.

> 
> Anyway, please do not reopen this bug. Please work on making uclibc more
> compatible with glibc, or send a convincing patch, but just reopening this
> bug will just piss us off, as we believe the onus here is on uclibc, not
> every indvidual program using libc.

i'll reopen this bug until the issue is fixed, and turning uclibc into glibc
just because you say so is not going to happen.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140117/2ec48fd4/attachment.html>