All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:28:30 +0000	[thread overview]
Message-ID: <bug-11366-163-3qKa1AFHZx@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 #8 from J.F. <jfdoyon@gmail.com> ---
See recently attached files.

This will need to be tested on a normally functioning linux host with SysV IPC
Message Q's running. Notably, use ipcs to make sure the message Q is cleaned up
properly after the test. The code is there and quite simple, but I can't test
it.

Also, the autoreconf setup is a little out of the ordinary, due to some
out-of-the ordinary libtool requirements by fakeroot it seems.

This now works cleanly on current Ubuntu for WSL.

Let me know if you have more suggestions for improvements?

Cheers,
J.F.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-09-24 15:28 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 [this message]
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-3qKa1AFHZx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.