From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11366] [2018.08] SysV IPC not available for fakeroot on WSL
Date: Mon, 04 Nov 2019 21:29:03 +0000 [thread overview]
Message-ID: <bug-11366-163-SMqK18SE3v@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11366-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11366
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #12 from Peter Korsgaard <jacmet@uclibc.org> ---
Fixed by:
https://git.buildroot.org/buildroot/commit/?id=fd1bcce9894773d7e1c1ca5be0f04b0b32128a1d
commit fd1bcce9894773d7e1c1ca5be0f04b0b32128a1d
Author: Matt Weber <matthew.weber@rockwellcollins.com>
Date: Mon Sep 16 22:58:14 2019 -0500
package/fakeroot: test for SYSV IPC support
fakeroot can be built to either use SYSV IPC or TCP for message passing.
A bug was discovered where Microsoft Windows 10 Services for Linux
doesn't include support for SYSV IPC MsgQ. This patch adds support to
detect this case and automatically build fakeroot to use the TCP
transport instead (It is assumed a TCP transport would definitely have
more overhead then MsgQs so the default wasn't changed to TCP).
Fixes
https://bugs.busybox.net/show_bug.cgi?id=11366
Cc: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Jean-Francois Doyon <jfdoyon@gmail.com>
Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
[Arnout: use a post-patch hook and AUTORECONF=YES]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-11-04 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 20:33 [Buildroot] [Bug 11366] New: [2018.08] SysV IPC not available for fakeroot on WSL bugzilla at busybox.net
2018-09-23 20:46 ` [Buildroot] [Bug 11366] " bugzilla at busybox.net
2018-09-23 22:49 ` bugzilla at busybox.net
2018-09-24 1:47 ` bugzilla at busybox.net
2018-09-24 1:59 ` bugzilla at busybox.net
2018-09-24 6:48 ` bugzilla at busybox.net
2018-09-24 15:18 ` bugzilla at busybox.net
2018-09-24 15:21 ` bugzilla at busybox.net
2018-09-24 15:28 ` bugzilla at busybox.net
2018-09-24 23:37 ` bugzilla at busybox.net
2018-09-24 23:37 ` bugzilla at busybox.net
2018-09-24 23:57 ` bugzilla at busybox.net
2018-11-02 9:55 ` bugzilla at busybox.net
2019-03-12 9:24 ` bugzilla at busybox.net
2019-11-04 21:29 ` bugzilla at busybox.net [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11366-163-SMqK18SE3v@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox