From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH] net/passt: Fix build failure due to missing GIO dependency
Date: Fri, 18 Jul 2025 14:41:24 +0100 [thread overview]
Message-ID: <aHpPBCiuUBJxqHyx@redhat.com> (raw)
In-Reply-To: <20250718133110.1510978-1-lvivier@redhat.com>
On Fri, Jul 18, 2025 at 03:31:10PM +0200, Laurent Vivier wrote:
> The passt networking backend uses functions from the GIO library,
> such as g_subprocess_launcher_new(), to manage its daemon process.
> So, building with passt enabled requires GIO to be available.
>
> If we enable passt and disable gio the build fails during linkage with
> undefined reference errors:
>
> /usr/bin/ld: libsystem.a.p/net_passt.c.o: in function `net_passt_start_daemon':
> net/passt.c:250: undefined reference to `g_subprocess_launcher_new'
> /usr/bin/ld: net/passt.c:251: undefined reference to `g_subprocess_launcher_take_fd'
> /usr/bin/ld: net/passt.c:253: undefined reference to `g_subprocess_launcher_spawnv'
> /usr/bin/ld: net/passt.c:256: undefined reference to `g_object_unref'
> /usr/bin/ld: net/passt.c:263: undefined reference to `g_subprocess_wait'
> /usr/bin/ld: net/passt.c:268: undefined reference to `g_subprocess_get_if_exited'
> /usr/bin/ld: libsystem.a.p/net_passt.c.o: in function `glib_autoptr_clear_GSubprocess':
> /usr/include/glib-2.0/gio/gio-autocleanups.h:132: undefined reference to `g_object_unref'
> /usr/bin/ld: libsystem.a.p/net_passt.c.o: in function `net_passt_start_daemon':
> net/passt.c:269: undefined reference to `g_subprocess_get_exit_status'
>
> Fix this by adding an explicit weson dependency on GIO for the passt
> option.
> The existing dependency on linux is kept because passt is only available
> on this OS.
>
> Reported-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> meson.build | 1 +
> 1 file changed, 1 insertion(+)
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 :|
next prev parent reply other threads:[~2025-07-18 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 13:31 [PATCH] net/passt: Fix build failure due to missing GIO dependency Laurent Vivier
2025-07-18 13:41 ` Daniel P. Berrangé [this message]
2025-07-18 14:54 ` Thomas Huth
2025-09-25 10:13 ` Peter Maydell
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=aHpPBCiuUBJxqHyx@redhat.com \
--to=berrange@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).