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, 24 Sep 2018 01:47:25 +0000 [thread overview]
Message-ID: <bug-11366-163-paDpVaPaE1@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11366-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11366
--- Comment #3 from J.F. <jfdoyon@gmail.com> ---
findings so far:
OK, so WSL does have some SysV IPC, but no message Q's, which is the feature
needed by fakeroot/faked by default.
The cleanest way to test this appears to be to use the ipcmk utility provided
by the host util-linux package ... only if the user selects the host util
package in his config however. If ipcmk -Q returns 1, use TCP.
Also, the fakeroot package builds sysv OR tcp. In order to support both, you
run 2 builds, presumably configured as two packages. Ideally, you would build
only one, based on the availability opf message Qs, if at all possible.
So one option is to force the host-util-linux package with most programs (force
the relevant BR2 option on, or mor eprecisely, remove the option and always
have it on), and then re-package 2 fakeroots and then use ipcmk at run time to
select the right fakeroot.
Another might be to simply give users the ability to select "TCP Fakeroot" in
their config via a BR2 variable. Since this is an edge case, it seems it might
be simpler to just do it that way, not unlike the way the host OpenSSL and
libelf requirements exist for the kernel.
Since this dependency is on a kernel system call, there's no clean way to
simply patch the existing fakeroot package and configure script ONLY, as Thomas
suggested. Maybe I could patch the configure script to use ipcmk however ... ?
I know *nothing* about how to work with autoconf however :P Because normally
you would build this tool as part of a distro on a separate host, dynamic
detection of IPC Message Q's would be of limited value "upstream" to the
fakeroot developers anyways ...
I think i would tend towards providing a user selectable config for "TCP
fakeroot" as a my favourite solution.
Thoughts?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-09-24 1:47 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 [this message]
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
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-paDpVaPaE1@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