if you use D-Bus on non-Linux Unix, please try new DBusSocket code
prlw1 at cam.ac.uk
Wed Apr 8 03:03:45 PDT 2015
On Tue, Mar 31, 2015 at 01:35:40PM +0100, Simon McVittie wrote:
> On <https://bugs.freedesktop.org/show_bug.cgi?id=89444> we've been
> working on fixing the distinction between file descriptors and sockets,
> which are the same thing on Unix, but unfortunately not on Windows
> (where a SOCKET is basically a uintptr_t, if done correctly).
> The solution we're trying is to introduce an internal DBusSocket struct
> containing an int (on Unix) or a SOCKET (on Windows), to force APIs to
> distinguish between the native thing and the abstraction.
> If you use D-Bus on non-Linux Unix platforms (*BSD, Solaris, etc.) it's
> possible that this will cause compilation failures, if I missed code
> paths that are not compiled on Linux. So, please try compiling, and
> preferably testing, this branch on your favourite Unix platform:
> git clone -b dbussocket git://people.freedesktop.org/~smcv/dbus
> web: http://cgit.freedesktop.org/~smcv/dbus/log/?h=dbussocket
> and report any problems on #89444, ideally with patches. The fix for any
> compilation errors will probably be something quite simple, like
> replacing "getsomesocketthing (s)" with "getsomesocketthing (s.fd)".
FWIW tests pass on NetBSD-current/amd64 (apart from my traditional
GThread issue). (There are just some warnings about documentation
More information about the dbus