In manual/errno.texi, 118 is assigned twice: both to ENOTSUP and to
not compilable on systems that make use of these numbers for defining
E* constants (the Hurd, for instance).
Created attachment 1510 [details]
Here is a proposed patch.
ECANCELED is only supported for aio functions, which have yet no implementation
on the Hurd: the symbols aren't even provided, so no existing program may have
already been compiled using that 118 value. That's why it is safe to change
that constant rather than ENOTSUP.
So, what do you think of this? This is currently blocking building kdelibs on Debian, I'd like to know how this should be fixed before submitting a patch to debian's glibc package.
This patch has been applied; now `mach/hurd/bits/errno.h' has to be regenerated.
A patch has been posted in
The .texi patch was applied, it looks like this is just an issue for a Hurd header now.
In my view we should add both Samuel and Thomas to <http://sourceware.org/glibc/wiki/MAINTAINERS> as maintainers of the Hurd support - that is, people who can review and commit changes to Hurd-specific code (both Hurd-specific files and Hurd-specific parts of other files where the usual coding conventions are observed) - they are the main people contributing to Hurd support. Roland, any thoughts on this?
I should continue to review nontrivial Hurd changes.
But certainly Samuel and Thomas should both be committers able to do trivial fixes and to commit on my approval.
Author: Samuel Thibault <email@example.com>
AuthorDate: Sun Jul 22 13:50:04 2007 +0200
Commit: Thomas Schwinge <firstname.lastname@example.org>
CommitDate: Sun Nov 4 22:15:29 2012 +0100
[BZ #3665] Regenerate sysdeps/mach/hurd/bits/errno.h.
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.