From: Jan Kiszka <jan.kiszka@siemens.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] Breakage
Date: Mon, 17 Sep 2012 22:17:38 +0200 [thread overview]
Message-ID: <50578562.7050607@siemens.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1209172354080.12891@linmac>
On 2012-09-17 21:54, 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
pcspk is not supposed to be specified like this. It's automatically
built for those targets that support it.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-09-17 20:17 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
2012-09-17 20:17 ` Jan Kiszka [this message]
-- 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=50578562.7050607@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=anthony@codemonkey.ws \
--cc=av1474@comtv.ru \
--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).