From: Blue Swirl <blauwirbel@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Consul <void@aleksoft.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows runtime error
Date: Fri, 22 May 2009 18:51:57 +0300 [thread overview]
Message-ID: <f43fc5580905220851j7277decch2367558633d797ac@mail.gmail.com> (raw)
In-Reply-To: <4A1609CD.4000904@codemonkey.ws>
On 5/22/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Consul wrote:
>
> > This commit breaks Windows giving runtime error "Unknown device
> 'virtio-balloon-pci'"
> >
> > ec6bd8dea77478f32981a5df49f66ca2430ad19d
> >
> > Author: Blue Swirl <blauwirbel@gmail.com> 2009-05-21 11:22:59
> > Committer: Blue Swirl <blauwirbel@gmail.com> 2009-05-21 11:22:59
> > Parent: 2567f5796c38238d6f2055f074e347a0338140ce (Compile
> most Xen files only once)
> >
> > Fix arm-softmmu breakage
> >
> > Don't use whole-archive for hwlib or libqemu objects
> >
> > Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> >
> hwlib definitely needs whole-archive.
No, it works fine without it.
> Why did this break arm-softmmu? It builds fine for me.
Because fdc.o was forced to be linked in with whole-archive but the
stuff that it depends on may be undefined on ARM. With whole-archive
removed from hwlib, fdc.o is not referenced in anywhere in arm-softmmu
and it will not be pulled in.
next prev parent reply other threads:[~2009-05-22 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 21:58 [Qemu-devel] Windows runtime error Consul
2009-05-22 2:11 ` Anthony Liguori
2009-05-22 12:04 ` Paul Brook
2009-05-22 13:07 ` Anthony Liguori
2009-05-22 13:15 ` Paul Brook
2009-05-22 15:48 ` Anthony Liguori
2009-05-22 16:12 ` Blue Swirl
2009-05-22 16:39 ` Anthony Liguori
2009-05-22 15:55 ` Blue Swirl
2009-05-22 16:36 ` Anthony Liguori
2009-05-24 9:14 ` Avi Kivity
2009-05-27 22:39 ` Anthony Liguori
2009-05-22 15:51 ` Blue Swirl [this message]
2009-05-22 16:35 ` Anthony Liguori
2009-05-22 16:53 ` Blue Swirl
2009-05-22 17:15 ` Paul Brook
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=f43fc5580905220851j7277decch2367558633d797ac@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=void@aleksoft.net \
/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).