qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, Bruce Majia <bruce.majia@gmail.com>
Subject: [Qemu-devel] Re: Build always fail on x86_32 host for i386_softmmu target
Date: Mon, 22 Mar 2010 14:44:58 +0100	[thread overview]
Message-ID: <4BA7745A.3040402@siemens.com> (raw)
In-Reply-To: <m3mxy0n3in.fsf@trasno.mitica>

Juan Quintela wrote:
> Bruce Majia <bruce.majia@gmail.com> wrote:
>> Hi,
>>
>> When I built qemu on my x86_32 host with following configure line:
>>
> 
> try to do first a:
> make distclean
> 
>> $ ./configure --prefix=/usr/local/qemus/master \
>> 	--target-list=i386-softmmu
>> $ make
> 
> there are several config.h & config.mak around (from old builds) you
> need to remove then 1st.

Doesn't the fact that this is required for a proper rebuild indicate
some issue in the build system? I just recall a recent multi-hour
debugging session of mine which turned out to be due to an inconsistent
build after moving forward in the git history (in qemu-kvm, but the code
change came from upstream). Or are there some fundamentally unresolvable
scenarios so that a distclean is mandatory after every git update?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-03-22 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  6:16 [Qemu-devel] Build always fail on x86_32 host for i386_softmmu target Bruce Majia
2010-03-22  8:31 ` Stefan Weil
2010-03-22  8:36   ` Bruce Majia
2010-03-22  8:50 ` [Qemu-devel] " Juan Quintela
2010-03-22 13:44   ` Jan Kiszka [this message]
2010-03-22 13:49     ` Juan Quintela
2010-03-22 13:57       ` Jan Kiszka
2010-03-22 14:05         ` Juan Quintela

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=4BA7745A.3040402@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=bruce.majia@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).