From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Hd6KK-0000gD-QA
	for qemu-devel@nongnu.org; Sun, 15 Apr 2007 11:07:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Hd6KJ-0000di-6P
	for qemu-devel@nongnu.org; Sun, 15 Apr 2007 11:07:40 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Hd6KJ-0000df-2w
	for qemu-devel@nongnu.org; Sun, 15 Apr 2007 11:07:39 -0400
Received: from moutng.kundenserver.de ([212.227.126.188])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <SRS0=1EpW=JS=mail.berlios.de=weil@srs.kundenserver.de>)
	id 1Hd6Fm-0004or-SX
	for qemu-devel@nongnu.org; Sun, 15 Apr 2007 11:02:59 -0400
Message-ID: <46223EA0.30104@mail.berlios.de>
Date: Sun, 15 Apr 2007 17:02:56 +0200
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [Patch] Makefile.target
References: <46222F54.3080702@weilnetz.de>
	<200704151504.29308.paul@codesourcery.com>
In-Reply-To: <200704151504.29308.paul@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: QEMU Developers <qemu-devel@nongnu.org>

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
>