From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Konstantin Kostiuk <kkostiuk@redhat.com>,
qemu-trivial@nongnu.org, Michael Roth <michael.roth@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] qga: Allow building of the guest agent without system emulators or tools
Date: Thu, 10 Nov 2022 10:57:27 +0100 [thread overview]
Message-ID: <0b29d9e3-9ce2-633c-1d73-cb5b0b9105ee@redhat.com> (raw)
In-Reply-To: <208d1191-6852-c74c-2a06-d65a6a657f4d@linaro.org>
On 10/11/2022 10.49, Philippe Mathieu-Daudé wrote:
> On 10/11/22 09:35, Thomas Huth wrote:
>> On 10/11/2022 06.49, Markus Armbruster wrote:
>>> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>>>
>>>> On 9/11/22 18:37, Thomas Huth wrote:
>>>>> If configuring with "--disable-system --disable-user --enable-guest-agent"
>>>>> the linking currently fails with:
>>>>>
>>>>> qga/qemu-ga.p/commands.c.o: In function `qmp_command_info':
>>>>> build/../../home/thuth/devel/qemu/qga/commands.c:70: undefined
>>>>> reference to `qmp_command_name'
>
>>>>> Let's make sure that we also compile and link the required files if
>>>>> the system emulators have not been enabled.
>>>>>
>>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>
>>> I wonder for how long this has been broken.
>>>
>>> Should we add such a configuration to CI?
>>
>> Some month ago, I'd say: Sure! ... but considering that gitlab now limits
>> the available CI minutes and that apparently nobody really cares about
>> this configuration (otherwise someone would have complained about this
>> earlier), I think it's not that important to have a separate CI test for
>> this configuration.
>
> We could eventually add a job restricted to qemu-project CI (not in
> forks).
The problem is: Who's going to create such jobs? Someone needs to write the
yaml stuff and test it first. And at least I pretty much lost motivation to
work on new yaml stuff, since this burns my private CI minutes (which I
rather need for my maintainer duties instead).
Thomas
next prev parent reply other threads:[~2022-11-10 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:37 [PATCH] qga: Allow building of the guest agent without system emulators or tools Thomas Huth
2022-11-09 17:50 ` Konstantin Kostiuk
2022-11-09 21:56 ` Philippe Mathieu-Daudé
2022-11-10 5:49 ` Markus Armbruster
2022-11-10 8:35 ` Thomas Huth
2022-11-10 9:49 ` Philippe Mathieu-Daudé
2022-11-10 9:57 ` Thomas Huth [this message]
2022-11-10 10:05 ` Daniel P. Berrangé
2022-11-10 8:31 ` Thomas Huth
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=0b29d9e3-9ce2-633c-1d73-cb5b0b9105ee@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).