From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Cc: Tyler James Leonhardt <tylerl0706@gmail.com>
Subject: Re: Zsh on Ubuntu on Windows
Date: Sat, 23 Apr 2016 14:40:10 -0700 [thread overview]
Message-ID: <CAH+w=7bYz8L8aHn2n2i_db1uqU_OZRXJOCnB7w4r8SCw1=ogqA@mail.gmail.com> (raw)
In-Reply-To: <CABGADBkdYt77GnUUzDpNpbabOMuk0Yn6TpE58r6gWg-1GHOMJw@mail.gmail.com>
On Sat, Apr 23, 2016 at 6:29 AM, Tyler James Leonhardt
<tylerl0706@gmail.com> wrote:
>
> Unfortunately, it hasn’t been working. I’m not sure if this is a zsh issue
> or if Microsoft’s subsystem for Ubuntu is just acting up. I found this
> issue on the oh-my-zsh repo:
>
> https://github.com/robbyrussell/oh-my-zsh/issues/4984
Based on the error message in that report, either zsh was compiled
with the wrong config.h settings or Microsoft's emulation of one of
the wait() family of system calls is incomplete. I don't know which
of the following #ifdef branches is being used --
#ifdef HAVE_WAIT3
# ifdef HAVE_GETRUSAGE
struct rusage ru;
pid = wait3((void *)&status, WAITFLAGS, &ru);
# else
pid = wait3((void *)&status, WAITFLAGS, NULL);
# endif
#else
# ifdef HAVE_WAITPID
pid = waitpid(-1, &status, WAITFLAGS);
# else
pid = wait(&status);
# endif
#endif
-- but the error message indicates that the returned pid == -1 and
errno has been set to "invalid argument", so something is askew in
whichever branch it was.
Who compiled the zsh you are using?
next prev parent reply other threads:[~2016-04-23 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 12:51 Tyler James Leonhardt
2016-04-23 13:18 ` Jérémie Roquet
2016-04-23 13:29 ` Tyler James Leonhardt
2016-04-23 14:11 ` Tyler James Leonhardt
2016-04-23 20:17 ` Jérémie Roquet
2016-04-23 21:40 ` Bart Schaefer [this message]
2016-04-23 23:42 ` Tyler James Leonhardt
2016-04-24 0:21 ` Bart Schaefer
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='CAH+w=7bYz8L8aHn2n2i_db1uqU_OZRXJOCnB7w4r8SCw1=ogqA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=tylerl0706@gmail.com \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).