qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>, qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com, stefanha@redhat.com,
	marcandre.lureau@redhat.com,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Fam Zheng" <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] slirp: Enable fork_exec support on Windows
Date: Mon, 26 Nov 2018 15:09:47 +0100	[thread overview]
Message-ID: <b9c8191b-176b-5285-e9ca-8d4267fc5a89@redhat.com> (raw)
In-Reply-To: <20181120005701.9304-1-samuel.thibault@ens-lyon.org>

Hi Samuel,

On 20/11/18 1:57, Samuel Thibault wrote:
> g_spawn_async_with_fds is portable on Windows, so we can now enable
> fork_exec support there.
> 
> Thanks Daniel P. Berrangé for the notice!

On x86_64 you can build locally using Docker:

$ make docker-test-build@debian-win32-cross
  BUILD   debian-win32-cross
  COPY    RUNNER
    RUN test-build in qemu:debian-win32-cross
Configure options:
--enable-werror --target-list=x86_64-softmmu,aarch64-softmmu
--prefix=/tmp/qemu-test/install --cross-prefix=i686-w64-mingw32.shared-
  CC      qga/commands-win32.o
  CC      qga/channel-win32.o
  CC      qga/service-win32.o
  CC      qga/vss-win32.o
...

>From the qemu source repository, you can also run once:
$ docker run --rm -it \
  -v $PWD:$PWD -w $PWD -v /tmp:/tmp \
  -u $UID \
  qemu:debian-win32-cross \
    bash -c 'mkdir build_win32 && cd build_win32 && ../configure
$QEMU_CONFIGURE_OPTS && make -j4'

Then to avoid rebuilding the world everytime, when you applied/modified
win32 related patches:

$ docker run --rm -it \
  -v $PWD:$PWD -w $PWD -v /tmp:/tmp \
  -u $UID \
  qemu:debian-win32-cross \
    bash -c 'make -C build_win32 -j4'

You can not 'run' the binary, but at least you can verify
compilation/linking steps.

Regards,

Phil.

> 
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
>   slirp/misc.c | 14 ++------------
>   1 file changed, 2 insertions(+), 12 deletions(-)
> 
> diff --git a/slirp/misc.c b/slirp/misc.c
> index 7972b9b05b..59b4e8f31c 100644
> --- a/slirp/misc.c
> +++ b/slirp/misc.c
> @@ -62,17 +62,6 @@ int add_exec(struct ex_list **ex_ptr, void *chardev, const char *cmdline,
>   }
>   
>   
> -#ifdef _WIN32
> -
> -int
> -fork_exec(struct socket *so, const char *ex)
> -{
> -    /* not implemented */
> -    return 0;
> -}
> -
> -#else
> -
>   static int
>   slirp_socketpair_with_oob(int sv[2])
>   {
> @@ -132,7 +121,9 @@ err:
>   static void
>   fork_exec_child_setup(gpointer data)
>   {
> +#ifndef _WIN32
>       setsid();
> +#endif
>   }
>   
>   int
> @@ -177,7 +168,6 @@ fork_exec(struct socket *so, const char *ex)
>       qemu_set_nonblock(so->s);
>       return 1;
>   }
> -#endif
>   
>   char *slirp_connection_info(Slirp *slirp)
>   {
> 

      parent reply	other threads:[~2018-11-26 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  0:57 [Qemu-devel] [PATCH] slirp: Enable fork_exec support on Windows Samuel Thibault
2018-11-20  6:00 ` Marc-André Lureau
2018-11-20  9:46 ` Daniel P. Berrangé
2018-11-26 14:09 ` Philippe Mathieu-Daudé [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=b9c8191b-176b-5285-e9ca-8d4267fc5a89@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=famz@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefanha@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).