From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch] Makefile.target
Date: Sun, 15 Apr 2007 21:33:33 +0100 [thread overview]
Message-ID: <200704152133.34580.paul@codesourcery.com> (raw)
In-Reply-To: <46223EA0.30104@mail.berlios.de>
> But nevertheless, sometimes it happens that I "do that",
> and then I'm always happy when I get a clear error
> message. Or even better, when something works as
> expected even when I did something unexpected.
> You are lucky if you never experienced such situations.
>
> In my case, even a simple line like
> $(DYNGEN):
> in Makefile.target would have made me happier.
I still think you're poking around in things that shouldn't concern you, so
deserve everything you get.
> "make subdir-i386-softmmu" is ok for my application,
> configuring with --target-list=i386-softmmu is no solution though
> because I need mips-softmmu and mipsel-softmmu, too :-)
So configure with --target-list=i386-softmmu,mips-softmmu,mipsel-softmmu
Paul
prev parent reply other threads:[~2007-04-15 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 13:57 [Qemu-devel] [Patch] Makefile.target Stefan Weil
2007-04-15 14:04 ` Paul Brook
2007-04-15 15:02 ` Stefan Weil
2007-04-15 20:33 ` Paul Brook [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=200704152133.34580.paul@codesourcery.com \
--to=paul@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).