From: "Michael S. Tsirkin" <mst@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: F10 build failure
Date: Sun, 29 Nov 2009 13:08:39 +0200 [thread overview]
Message-ID: <20091129110839.GA24654@redhat.com> (raw)
In-Reply-To: <m3r5rlw2zl.fsf@neno.neno>
On Thu, Nov 26, 2009 at 07:33:02PM +0100, Juan Quintela wrote:
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > Hi!
> > qemu build on fedora 10 fails with:
> > /root/scm/qemu/fpu/softfloat-native.c:132:5: error: "HOST_LONG_BITS" is not defined
> > make[1]: *** [fpu/softfloat-native.o] Error 1
> > make: *** [subdir-x86_64-softmmu] Error 2
> >
> > just sticking
> >
> > #define HOST_LONG_BITS 64
> >
> > in fpu/softfloat-native.c helps, but what is the correct
> > fix?
>
> rm */config.h
>
> You updated from an old tree, right?
>
> Later, Juan.
Yes. That helped, but I am surprised simply re-running configure was
insufficient.
--
MST
next prev parent reply other threads:[~2009-11-29 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 15:52 [Qemu-devel] F10 build failure Michael S. Tsirkin
2009-11-26 18:33 ` [Qemu-devel] " Juan Quintela
2009-11-29 11:08 ` Michael S. Tsirkin [this message]
2009-11-29 20:56 ` 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=20091129110839.GA24654@redhat.com \
--to=mst@redhat.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).