From: Thomas Huth <thuth@redhat.com>
To: "Howard Spoelstra" <hsp.cat7@gmail.com>,
"qemu-devel qemu-devel" <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] Bug: Lost slirp functionality on qemu-system-ppc build for windows.
Date: Mon, 11 Feb 2019 08:56:11 +0100 [thread overview]
Message-ID: <0be24d4d-19e3-0c4a-e414-ed61b043f1cb@redhat.com> (raw)
In-Reply-To: <CABLmASFLwswYELUGHKjZct6XnEYb4tKn1XEuCAgwniN7NM110g@mail.gmail.com>
On 2019-02-10 23:12, Howard Spoelstra wrote:
> Hi,
>
> I just cross compiled Qemu-system-ppc for Windows on Fedora 29 and
> discovered slirp does not work anymore. Tap networking works fine.
> Bisecting got me here:
>
> a9d8b3ec4385793815d7121785730422fa3dfb68 is the first bad commit
> commit a9d8b3ec4385793815d7121785730422fa3dfb68
> Author: Marc-André Lureau <marcandre.lureau@redhat.com>
> Date: Thu Jan 17 15:43:52 2019 +0400
>
> slirp: replace remaining qemu headers dependency
>
> Except for the migration code which is gated by WITH_QEMU, only
> include our own headers, so libslirp can be built standalone.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
>
> :040000 040000 cd06df21ed96497cd12f2a20adb3d66cb0da8010
> ab5afd3f50910e39b2b700722cd47de8f0cf9e2c M slirp
Thanks for bisecting the issue already! ... adding Marc-André and Samuel
to the thread, maybe they have a clue what might be wrong here...
Thomas
next prev parent reply other threads:[~2019-02-11 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 22:12 [Qemu-devel] Bug: Lost slirp functionality on qemu-system-ppc build for windows Howard Spoelstra
2019-02-11 7:56 ` Thomas Huth [this message]
2019-02-11 9:52 ` Peter Maydell
2019-02-11 16:06 ` Marc-André Lureau
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=0be24d4d-19e3-0c4a-e414-ed61b043f1cb@redhat.com \
--to=thuth@redhat.com \
--cc=hsp.cat7@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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.
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).