qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Hu Tao <hutao@cn.fujitsu.com>
Subject: Re: [Qemu-devel] GIT master fails compilation for ACPI
Date: Fri, 22 Nov 2013 18:07:15 +0100	[thread overview]
Message-ID: <528F8F43.4080202@redhat.com> (raw)
In-Reply-To: <54035371.127078.1385118997906.open-xchange@email.1und1.de>

Il 22/11/2013 12:16, Erik Rull ha scritto:
> It's getting more and more complex to build qemu, is there a reason why everyone
> needs to build the acpi stuff by himself?

It is only attempted if iasl is installed but as you said below, your
version is too old.  Please run "make V=1" so that we can see what is
the problem.

> It should be something static like the bios binary files, right?

ACPI tables are now generated by QEMU, so the ACPI compilation step
happens while compiling QEMU.

> So you could provide the defaults directly and everyone that wants to modify the
> defaults is free to compile it by himself.
> 
> And if these tools are required, please add an error message at configure
> runtime so that the successive errors at runtime will not appear, because
> compiling is then blocked by configure. And if the IASL is too old, a version
> check at configure runtime would be helpful as well.

Good idea.  Any chance you could help?  Version 20090123 should be new
enough.

Paolo

  parent reply	other threads:[~2013-11-22 17:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  8:06 [Qemu-devel] GIT master fails compilation for ACPI Erik Rull
2013-11-21  8:36 ` Hu Tao
2013-11-21 20:44   ` Erik Rull
2013-11-22 10:56     ` Stefan Hajnoczi
2013-11-22 11:16       ` Erik Rull
2013-11-22 15:53         ` Stefan Hajnoczi
2013-11-22 17:07         ` Paolo Bonzini [this message]
2013-11-22 20:19           ` Erik Rull
2013-11-24 11:28             ` Michael S. Tsirkin
2013-11-25 20:08               ` Erik Rull
2013-11-25 20:34                 ` Michael S. Tsirkin

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=528F8F43.4080202@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=erik.rull@rdsoftware.de \
    --cc=hutao@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).