qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Bug 1373362] Re: qemu-2.1.1 i386-softmmu compile error


From: Peter Maydell
Subject: Re: [Qemu-devel] [Bug 1373362] Re: qemu-2.1.1 i386-softmmu compile error: q35_dsdt_applesmc_sta undeclared
Date: Sat, 27 Sep 2014 11:49:02 +0100

On 27 September 2014 10:28, Thomas Eschenbacher
<address@hidden> wrote:
> update: I found out that the latest version on the stable-1.7 branch builds 
> fine, but all stable-2.0 and later fail.
> I did some binary search on all versions on the stable-2.0 branch and found 
> out that the problem occurs after this commit:
>
> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=15bce1b7c55c69f47e13c9eb2a4b80f41da26581

Do you also see this compile failure on git master, or is
it only a problem on the stable branch?

> Unfortunately this is not so much surprising, as this is the first
> commit that introduced a reference to that symbol. So the question is:
> where is that symbol defined in *your* version?
>
> Just to track this down: could you please do a "grep" in your source to see 
> where it is defined on your side?
> (grep -r q35_dsdt_applesmc_sta ../)
> I expect there is some slight difference to the hits that I get here (see my 
> initial post)
>
> My guess is that it is defined in some "generated" file and that there
> is a problem with the generator/converter that produces it.

Note that there are two different possible paths here:
 * if configure finds you have iasl it will build the
   q35-acpi-dsdt.hex files from the dsl source files
 * otherwise, we just copy hw/i386/q35-acpi-dsdt.hex.generated
   into the build tree as the .hex file
(at least, this is how master is doing it.)

Some things that might be useful for debugging:
 * if you add "V=1" to your make command line it will print the
   full commands being run rather than the pretty "IASL/CPP/CC"
   short progress info
 * you could look at whether the .hex file you've generated
   matches the .hex.generated file we ship at all

My guess is that your system has a busted iasl of some kind,
in which case you can work around this by passing '--iasl=none'
to configure, but it would be good to identify what's actually
going wrong here.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]