1. 08 Oct, 2013 2 commits
  2. 16 Sep, 2013 2 commits
    • Simon McVittie's avatar
      Remove support for platforms with no 64-bit integer type · b47d5062
      Simon McVittie authored
      This has been a soft requirement since 1.5.0; anyone on such platforms
      would have had to configure --without-64-bit, provoking a warning that
      instructed them to report a D-Bus bug with details of their platform.
      Nobody has done so, so if anyone still lacks a 64-bit integer type,
      they're on their own.
      
      (Also, I tried the build with --without-64-bit and it's full of
      fatal compiler warnings, so it's not clear that we're actually
      losing anything by removing this "feature".)
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65429Reviewed-by: default avatarChengwei Yang <chengwei.yang@intel.com>
      b47d5062
    • Simon McVittie's avatar
      dbus-sysdeps-win: don't include wspiapi.h · 3b9c2817
      Simon McVittie authored
      This block provoked a warning on mingw-w64 because we were redefining
      _inline. According to Ralf's research, it was introduced in 452ff68a:
      Windows 2000 doesn't have getaddrinfo and related functions in
      ws2tcpip.h, but does have a shim implementation in wspiapi.h.
      
      At the time of 452ff68a, mingw32 didn't have wspiapi.h, so it's unclear
      why there was a __GNUC__ code path here. The "#define _inline" on that
      code path looks likely to be some sort of workaround for a faulty version
      of wspiapi.h? Current mingw-w64 does have wspiapi.h, so we enter the
      __GNUC__ code path and get the redefinition.
      
      dbus no longer supports Windows 2000, so we no longer need wspiapi.h
      at all, and can rely on XP or later. (Ralf's policy is to only support
      versions of Windows that are still supported by Microsoft, and Windows 2000
      reached the end of its life-cycle in 2010.)
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=68852
      Reviewed-by: Ralf Habacker
      3b9c2817
  3. 13 Sep, 2013 2 commits
  4. 05 Sep, 2013 2 commits
  5. 03 Sep, 2013 1 commit
    • Simon McVittie's avatar
      Tests: allow dbus-glib to be replaced with use of libdbus-internal · 30e7a813
      Simon McVittie authored
      We only use dbus-glib for its main loop; within dbus, DBusLoop is
      available as an alternative, although it isn't thread-safe and
      isn't public API.
      
      For tests that otherwise only use libdbus public API, it's desirable to
      be able to avoid DBusLoop, so we can run them against an installed
      libdbus as an integration test. However, if we don't have dbus-glib,
      we're going to have to use an in-tree main loop, which might as well
      be DBusLoop.
      
      The major disadvantage of using dbus-glib is that it isn't safe to
      link both dbus-1 and dbus-internal at the same time. This is awkward
      for a future test case that wants to use _dbus_getsid() in dbus-daemon.c,
      but only on Windows (fd.o #54445). If we use the same API wrapper around
      both dbus-glib and DBusLoop, we can compile that test against dbus-glib
      or against DBusLoop, depending on the platform.
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=68852Reviewed-by: Ralf Habacker's avatarRalf Habacker <ralf.habacker@freenet.de>
      30e7a813
  6. 22 Aug, 2013 1 commit
  7. 28 Jun, 2013 2 commits
  8. 25 Jun, 2013 1 commit
  9. 13 Jun, 2013 1 commit
  10. 12 Jun, 2013 3 commits
  11. 06 Jun, 2013 2 commits
  12. 05 Jun, 2013 1 commit
  13. 02 May, 2013 1 commit
  14. 25 Apr, 2013 1 commit
  15. 24 Apr, 2013 2 commits
  16. 18 Apr, 2013 1 commit
  17. 11 Apr, 2013 1 commit
    • Matt Fischer's avatar
      Set default maximum number of Unix fds according to OS · 97729354
      Matt Fischer authored
      QNX has an arbitrary limit to the number of file descriptors
      which may be passed in a message, which is smaller than the
      current default.  This patch therefore changes the default from
      a hardcoded constant to a macro, which is determined at configure
      time by looking at the host operating system.
      
      [This reduces the limit from 4096 (session)/1024 (system) to 128 fds
      per message on QNX, and 1024 fds per message on other operating systems.
      I think the reduced session bus limit on other OSs is a reasonable change
      too, given that the default hard/soft ulimits in Linux are only 4096/1024
      fds per process. -smcv]
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=61176
      Reviewed-by: Simon McVittie <simon.mcvittie.collabora.co.uk>
      97729354
  18. 05 Apr, 2013 3 commits
  19. 03 Apr, 2013 1 commit
  20. 22 Feb, 2013 3 commits
  21. 14 Feb, 2013 2 commits
  22. 19 Nov, 2012 1 commit
    • Simon McVittie's avatar
      configure: redo pthread check to check for more things · 277675a4
      Simon McVittie authored
      In principle, anything in the pthread namespace might either be in the
      platform-specific thread library (libpthread or libpthreads or libthreads
      or ...), or in libc.
      
      In particular, it seems that pthread_mutexattr_init and
      pthread_mutexattr_settype are in libpthread, not libc, on Linux. We
      previously didn't (intentionally) look for them in libpthread, only
      in libc; so this check deserved to fail.
      
      However, a faulty configure check for pthread_cond_timedwait
      worked around this on Linux by checking for -lpthread and adding it
      to THREAD_LIBS if pthread_cond_timedwait *was* found in libc (even
      though that behaviour makes no sense).
      
      The practical impact was that D-Bus would fail to compile on platforms
      where pthread_cond_timedwait is in a special threading library that
      is not linked by default, and at least one of
      (pthread_mutexattr_init, pthread_mutexattr_settype) is also in a
      special threading library. This is the case on at least OpenBSD
      (fd.o #54416).
      
      So far I've only added checks for the new symbols introduced by
      using recursive pthreads mutexes. If we get reports of compilation
      failures on weird platforms, we can check for more symbols.
      
      Also clarify the indentation, which was turning into quite a mess,
      and use AS_IF instead of if/elif/else/fi in accordance with Autoconf
      best-practice.
      
      Bug: https://bugs.freedesktop.org/show_bug.cgi?id=47239Reviewed-by: Colin Walters's avatarColin Walters <walters@verbum.org>
      277675a4
  23. 02 Oct, 2012 1 commit
  24. 28 Sep, 2012 3 commits