From: Paul Bolle <pebolle@tiscali.nl>
To: Juan Quintela <quintela@trasno.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Fix *-user build error
Date: Tue, 13 Oct 2009 13:22:35 +0200 [thread overview]
Message-ID: <1255432955.1817.23.camel@localhost.localdomain> (raw)
In-Reply-To: <m3tyy336d2.fsf@neno.mitica>
On Tue, 2009-10-13 at 13:01 +0200, Juan Quintela wrote:
> Paul Bolle <pebolle@tiscali.nl> wrote:
> > Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> > ---
> > Currently building i386-linux-user fails with this error:
> >
> > CC i386-linux-user/fpu/softfloat-native.o
> > [...]/qemu/fpu/softfloat-native.c:132:5: error: "HOST_LONG_BITS" is not defined
> > make[3]: *** [fpu/softfloat-native.o] Error 1
> > make[2]: *** [all] Error 2
> > make[1]: *** [subdir-i386-linux-user] Error 2
> > make: *** [build-all] Error 2
> >
>
> make disclean
> or
> rm -f */config.h
>
> Will fix the problem.
>
> config.h was a generated file, and now it is not :( To make things more
> interesting, it moved from one place to other (now it is shared for all
> targets).
make distclean didn't help here (neither did "make clean", which is what
I used before submitting the trivial patch).
"rm */config.h" did work. Thanks.
Why doesn't "make clean" do what one expects it to do? Can't it be made
to behave properly?
Paul
next prev parent reply other threads:[~2009-10-13 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 9:32 [Qemu-devel] [PATCH] Fix *-user build error Paul Bolle
[not found] ` <m3tyy336d2.fsf@neno.mitica>
2009-10-13 11:22 ` Paul Bolle [this message]
[not found] ` <m3aazv1jox.fsf@neno.mitica>
2009-10-13 15:58 ` [Qemu-devel] " Paul Bolle
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=1255432955.1817.23.camel@localhost.localdomain \
--to=pebolle@tiscali.nl \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).