From: Peter Maydell <peter.maydell@linaro.org>
To: Claudio Fontana <claudio.fontana@huawei.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] implement smbios support for mach-virt: triggers usual QEMU makefile bug
Date: Mon, 5 Oct 2015 11:11:06 +0100 [thread overview]
Message-ID: <CAFEAcA9vK+of5iNQy38yz1Y6ku+GfFMy+aF=pKvWgOgTXLaeMw@mail.gmail.com> (raw)
In-Reply-To: <56123612.3090100@huawei.com>
On 5 October 2015 at 09:34, Claudio Fontana <claudio.fontana@huawei.com> wrote:
> Hi Peter,
>
> The commit "smbios: implement smbios support for mach-virt" seems to cause the usual problem in QEMU's makefiles to trigger:
>
> hw/arm/virt.c:892: undefined reference to `smbios_set_defaults'
> hw/arm/virt.c:895: undefined reference to `smbios_get_tables'
>
> This is IIRC the consequence of adding CONFIG_SMBIOS=y to default-configs/rm-softmmu.mak,
> which is not picked up by the build system until a clean of the working tree has been done, right?
>
> This is worked around by
>
> $ git clean -d -x -f
>
> followed by reconfigure/rebuild. Just wanted to mention this on the
> list in case someone is looking to fix this longstanding issue..
You can also just remove $BUILDDIR/aarch64-softmmu-config-devices.mak.d
I think, which will cause us to realise we need to regenerate
config-devices.mak.
I haven't ever been able to figure out why this stuff fails. We have
had several bugs in the past here, and if you have a build-tree that
predates those getting fixed you can have stale stuff in the tree
that means that even after the makefile fixes they still don't take
effect. But I suspect there's still a bug in there somewhere.
thanks
-- PMM
prev parent reply other threads:[~2015-10-05 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 8:34 [Qemu-devel] implement smbios support for mach-virt: triggers usual QEMU makefile bug Claudio Fontana
2015-10-05 10:11 ` Peter Maydell [this message]
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='CAFEAcA9vK+of5iNQy38yz1Y6ku+GfFMy+aF=pKvWgOgTXLaeMw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=claudio.fontana@huawei.com \
--cc=pbonzini@redhat.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).