From: malc <av1474@comtv.ru>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Breakage
Date: Tue, 18 Sep 2012 15:31:50 +0400 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1209181527550.2424@linmac> (raw)
In-Reply-To: <CAMo8BfLDECC1c=yCX1mxsf-Qxp7g4L8e_+j6zCcfZ9=ioaYjVw@mail.gmail.com>
On Tue, 18 Sep 2012, Max Filippov wrote:
> On Tue, Sep 18, 2012 at 12:15 AM, Eduardo Habkost <ehabkost@redhat.com> wrote:
> > On Mon, Sep 17, 2012 at 11:54:42PM +0400, malc wrote:
> >> On Mon, 17 Sep 2012, Anthony Liguori wrote:
> >>
> >> > malc <av1474@comtv.ru> writes:
> >> >
> >> > > Some(thing|one) broke compilation with pcspk enabled.
> >> > > Symptoms being:
> >> > >
> >> > > ../libhw32/hw/pcspk.o: In function `pcspk_io_write':
> >> > > /home/malc/x/rcs/git/qemu/hw/pcspk.c:145: undefined reference to `pit_set_gate'
> >> > > ../libhw32/hw/pcspk.o: In function `pcspk_io_read':
> >> > > /home/malc/x/rcs/git/qemu/hw/pcspk.c:130: undefined reference to `pit_get_channel_info'
> >> > > ../libhw32/hw/pcspk.o: In function `pcspk_callback':
> >> > > /home/malc/x/rcs/git/qemu/hw/pcspk.c:81: undefined reference to `pit_get_channel_info'
> >> > > collect2: ld returned 1 exit status
> >> >
> >> > Try cleaning your build directory.
> >> >
> >> > It builds fine for me.
> >> >
> >>
> >> --target-list=xtensa-softmmu --audio-card-list=pcspk
> >
> > It looks like this particular configuration never worked, since
> > xtensa-softmmu was introduced (commit cfa550c6acc6718c3f932e858366e3e1e81266d6).
>
> Other embedded platforms (I've tried cris-softmmu, lm32-softmmu, or32-softmmu,
> sh4-softmmu) give the same result.
>
> > Does it even make sense to have a PC-speaker on a Xtensa machine?
> > Should the machine have a i8254 PIT?
>
> I doubt that it's meaningful for any of the mentioned _architectures_,
> definitely not for xtensa.
>
Condensed version of long story:
I have a script that invokes QEMU's configure with tons of command line
arguments (i.e. turn on most of the audio drivers, most of the audio
cards, disable stuff i don't have or need; enable ccache and so forth),
this script was used to configure xtensa-softmmu configure never
complained but the make later bombed in the way mentioned above.
To avoid this "surprise" result we can(should?) filter out the
cards requested by the user based on contents of audio_possible_card_list
(in a fashion similar to the one employed for driver list filtering)
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2012-09-18 11:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 17:40 [Qemu-devel] Breakage malc
2012-09-17 19:35 ` Anthony Liguori
2012-09-17 19:54 ` malc
2012-09-17 20:15 ` Eduardo Habkost
2012-09-17 22:41 ` Max Filippov
2012-09-18 11:31 ` malc [this message]
2012-09-17 20:17 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2012-03-18 16:12 malc
2012-03-18 16:16 ` Avi Kivity
2012-03-18 16:21 ` malc
2012-03-19 16:16 ` Luiz Capitulino
2012-03-19 4:34 ` Roy Tam
2012-03-19 9:48 ` Avi Kivity
2012-03-20 1:21 ` Roy Tam
2009-08-26 20:56 malc
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=alpine.LNX.2.00.1209181527550.2424@linmac \
--to=av1474@comtv.ru \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=jcmvbkbc@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).