From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/7] audio: modularize
Date: Tue, 6 Mar 2018 12:42:33 +0100 [thread overview]
Message-ID: <20180306114232.v5gtwxald4mmelab@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAJ+F1CK5MsZ5=-z2yWznBcHjZqskHSdiyYxC30azEcQ9AXrRLg@mail.gmail.com>
On Tue, Mar 06, 2018 at 12:22:49PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Tue, Mar 6, 2018 at 8:40 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > Add audio driver (host backend) registry. Add audio module support.
> > Enable module builds for alsa, oss, pulse and sdl.
> >
> > Gerd Hoffmann (7):
> > audio: add driver registry
> > audio: add module loading support
> > build: enable audio modules
> > audio/alsa: build as module
> > audio/oss: build as module
> > audio/pulseaudio: build as module
> > audio/sdl: build as module
> >
>
> Is this a problem on my side? (configure
> '--audio-drv-list=oss,alsa,pa,sdl' '--enable-modules')
>
> elmarco@boraha:~/src/qemu/build (master %)$
> x86_64-softmmu/qemu-system-x86_64 -audio-help
> Failed to open module:
> /home/elmarco/src/qemu/build/x86_64-softmmu/../audio-oss.so: undefined
> symbol: _TRACE_OSS_INVALID_AVAILABLE_SIZE_DSTATE
> Failed to open module:
> /home/elmarco/src/qemu/build/x86_64-softmmu/../audio-alsa.so:
> undefined symbol: _TRACE_ALSA_XRUN_OUT_DSTATE
> Failed to open module:
> /home/elmarco/src/qemu/build/x86_64-softmmu/../audio-pa.so: undefined
> symbol: audio_pt_unlock_and_signal
> Failed to open module:
> /home/elmarco/src/qemu/build/x86_64-softmmu/../audio-sdl.so: undefined
> symbol: audio_pcm_sw_write
Works fine here. Tried "make clean && make"?
Qemu build system seems to not rebuild object files when the compiler
flags change. So you can't switch between --enable-modules and
--disable-modules without "make clean" inbetween. Same issue when
patches switch code from compiled-in to modular and you try an
incremental build.
I've seen only build failues due to this, not module load errors. But
possibly only because I stopped doing incremental builds when working on
module patches ...
cheers,
Gerd
next prev parent reply other threads:[~2018-03-06 11:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 7:40 [Qemu-devel] [PATCH 0/7] audio: modularize Gerd Hoffmann
2018-03-06 7:40 ` [Qemu-devel] [PATCH 1/7] audio: add driver registry Gerd Hoffmann
2018-03-06 10:58 ` Marc-André Lureau
2018-03-06 7:40 ` [Qemu-devel] [PATCH 2/7] audio: add module loading support Gerd Hoffmann
2018-03-06 10:59 ` Marc-André Lureau
2018-03-06 7:40 ` [Qemu-devel] [PATCH 3/7] build: enable audio modules Gerd Hoffmann
2018-03-06 7:40 ` [Qemu-devel] [PATCH 4/7] audio/alsa: build as module Gerd Hoffmann
2018-03-06 7:40 ` [Qemu-devel] [PATCH 5/7] audio/oss: " Gerd Hoffmann
2018-03-06 7:40 ` [Qemu-devel] [PATCH 6/7] audio/pulseaudio: " Gerd Hoffmann
2018-03-06 7:40 ` [Qemu-devel] [PATCH 7/7] audio/sdl: " Gerd Hoffmann
2018-03-06 11:22 ` [Qemu-devel] [PATCH 0/7] audio: modularize Marc-André Lureau
2018-03-06 11:42 ` Gerd Hoffmann [this message]
2018-03-06 12:43 ` Marc-André Lureau
2018-03-06 13:27 ` Gerd Hoffmann
2018-03-06 15:28 ` 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=20180306114232.v5gtwxald4mmelab@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@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).