From: Paolo Bonzini <pbonzini@redhat.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] work around make bug for *-user builds
Date: Tue, 27 Apr 2010 18:22:58 +0200 [thread overview]
Message-ID: <4BD70F62.30505@redhat.com> (raw)
In-Reply-To: <20100427162145.GM18198@codesourcery.com>
>>> To restore buildability of the *-user configs, move calls to set-vpath
>>> out from under ifdefs, and conditionally provide a path for set-vpath.
>>
>> Uhm, out of curiosity what make is this? Lots of patches have been
>> committed to *-user in the meanwhile, so it looks like a problem in your
>> make.
>
> This happens to me with three different versions of make:
>
> - 3.80, no patches applied.
> - 3.81, no patches applied.
> - 3.81 from Ubuntu Hardy (I haven't looked to see what patches are applied).
Interesting. BTW I am using Fedora. Given this,
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Paolo
prev parent reply other threads:[~2010-04-27 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 15:07 [Qemu-devel] [PATCH] work around make bug for *-user builds Nathan Froyd
2010-04-27 16:10 ` [Qemu-devel] " Paolo Bonzini
2010-04-27 16:21 ` Nathan Froyd
2010-04-27 16:22 ` Paolo Bonzini [this message]
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=4BD70F62.30505@redhat.com \
--to=pbonzini@redhat.com \
--cc=froydnj@codesourcery.com \
--cc=qemu-devel@nongnu.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).