From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Patch] Makefile.target
Date: Sun, 15 Apr 2007 17:02:56 +0200 [thread overview]
Message-ID: <46223EA0.30104@mail.berlios.de> (raw)
In-Reply-To: <200704151504.29308.paul@codesourcery.com>
Hi Paul,
of course it is always good practice to avoid errors.
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.
"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 :-)
Stefan
Paul Brook schrieb:
> On Sunday 15 April 2007 14:57, Stefan Weil wrote:
>> This small patch for Makefile.target fixes a very special build issue:
>>
>> make distclean # (only needed to remove files left from earlier builds)
>> ./configure
>> make -C i386-softmmu # (or any other system emulation)
>>
>> will try to build the missing dyngen and fail because dyngen is
>> normally build by the root Makefile.
>>
>> The patch adds a rule for dyngen which simply calls "make dyngen" in the
>> root directory.
>
> I think "don't do that" is the most appropriate response to this problem.
> It's certainly not something I'd like to commit to keeping working
> long-term.
>
> Try "make subdir-i386-softmmu" if you really must do this.
> Configuring with --target-list=i386-softmmu is a much better solution
> though.
>
> Paul
>
next prev parent reply other threads:[~2007-04-15 15:07 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 [this message]
2007-04-15 20:33 ` Paul Brook
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=46223EA0.30104@mail.berlios.de \
--to=weil@mail.berlios.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.