Bug 107051 - building tests fails on Windows (msys2)
Summary: building tests fails on Windows (msys2)
Status: RESOLVED MOVED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.12
Hardware: Other Windows (All)
: medium normal
Assignee: D-Bus Maintainers
QA Contact: D-Bus Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-27 13:46 UTC by Vincent Torri
Modified: 2018-10-12 21:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Vincent Torri 2018-06-27 13:46:19 UTC
when i compile d-bus on Windows (MSYS2 + mingw-w64), using the autotools, i get that error:

/usr/bin/mkdir -p -m 700 XDG_RUNTIME_DIR
/usr/bin/mkdir: impossible de modifier les droits de « XDG_RUNTIME_DIR »: Permission denied

(translation : impossible to modify access rights)

trying this command directly in MSYS2 gives the same error. So passing -m 700 seems wrong when using MSYS2

Vincent Torri
Comment 1 Simon McVittie 2018-08-30 19:01:57 UTC
We need an XDG_RUNTIME_DIR that is owned by the current user and cannot be written by any other users. I'm open to suggestions for how we should achieve that, in a way that can work on msys2?

We can't just use mkdir -p without specifying permissions, because if we did, a user running on Unix with "umask 002" would fail this check:

  if ((S_IWOTH | S_IWGRP) & buf.st_mode)
    {
      dbus_set_error (error, DBUS_ERROR_FAILED,
                      "%s \"%s\" can be written by others (mode 0%o)",
                      label, dir, buf.st_mode);
      return FALSE;
    }
Comment 2 GitLab Migration User 2018-10-12 21:35:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/216.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.