qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Jintao Yin" <nicememory@gmail.com>,
	"Yonggang Luo" <luoyonggang@gmail.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v2 1/2] gitlab-ci: Cover SPICE in the MSYS2 job
Date: Wed, 22 Mar 2023 18:22:28 +0000	[thread overview]
Message-ID: <ZBtHZGtEBchXzae1@redhat.com> (raw)
In-Reply-To: <20230322135721.61138-2-philmd@linaro.org>

On Wed, Mar 22, 2023 at 02:57:20PM +0100, Philippe Mathieu-Daudé wrote:
> Include the mingw-w64-x86_64-spice package so SPICE is covered:
> 
>   C compiler for the host machine: cc -m64 -mcx16 (gcc 12.2.0 "cc (Rev10, Built by MSYS2 project) 12.2.0")
>   ...
>   Run-time dependency spice-protocol found: YES 0.14.4
>   Run-time dependency spice-server found: YES 0.15.1
> 
> In particular this would have helped catching the build issue
> reported as https://gitlab.com/qemu-project/qemu/-/issues/1553:
> 
>   [1851/5253] Compiling C object libcommon.fa.p/ui_spice-core.c.obj
>   FAILED: libcommon.fa.p/ui_spice-core.c.obj
>   ../ui/spice-core.c: In function 'watch_remove':
>   ../ui/spice-core.c:152:5: error: implicit declaration of function 'qemu_close_to_socket' [-Werror=implicit-function-declaration]
>   152 |     qemu_close_to_socket(watch->fd);
>       |     ^~~~~~~~~~~~~~~~~~~~
>   ../ui/spice-core.c:152:5: error: nested extern declaration of 'qemu_close_to_socket' [-Werror=nested-externs]
> 
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> See https://gitlab.com/philmd/qemu/-/jobs/3980693656#L2378
> ---
>  .gitlab-ci.d/windows.yml | 2 ++
>  1 file changed, 2 insertions(+)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-03-22 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 13:57 [PATCH v2 0/2] ci: Remove cirrus-ci & cover SPICE in MSYS2 at gitlab-ci Philippe Mathieu-Daudé
2023-03-22 13:57 ` [PATCH v2 1/2] gitlab-ci: Cover SPICE in the MSYS2 job Philippe Mathieu-Daudé
2023-03-22 18:22   ` Daniel P. Berrangé [this message]
2023-03-22 13:57 ` [PATCH v2 2/2] cirrus-ci: Remove MSYS2 jobs duplicated with gitlab-ci Philippe Mathieu-Daudé
2023-03-22 18:37   ` Daniel P. Berrangé
2023-03-23  8:37     ` Thomas Huth
2023-03-23  9:24       ` Daniel P. Berrangé
2024-11-25 12:16   ` Thomas Huth
2024-11-25 13:32     ` Michael Tokarev
2023-03-22 14:28 ` [PATCH v2 0/2] ci: Remove cirrus-ci & cover SPICE in MSYS2 at gitlab-ci Richard Henderson

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=ZBtHZGtEBchXzae1@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=luoyonggang@gmail.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=nicememory@gmail.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@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).