From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:39245)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Sm1Ml-0003X3-CE
	for qemu-devel@nongnu.org; Tue, 03 Jul 2012 07:34:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Sm1Mf-0004Eh-Ni
	for qemu-devel@nongnu.org; Tue, 03 Jul 2012 07:33:58 -0400
Message-ID: <4FF2D889.4090306@redhat.com>
Date: Tue, 03 Jul 2012 13:33:29 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <20120627235055.GA9149@tyr.buserror.net>
	<4FF1D151.6050604@suse.de> <4FF1D4F8.1020708@freescale.com>
	<4FF20575.9090708@freescale.com> <4FF20B89.7030007@suse.de>
	<4FF20D85.20609@freescale.com>
	<4BF58A38-954C-49A8-BDBD-3CE15D379BBF@suse.de>
	<4FF20FAA.5000306@freescale.com>
	<17B4AA66-74DA-47D6-BB0B-12EA67B6C7F1@suse.de>
In-Reply-To: <17B4AA66-74DA-47D6-BB0B-12EA67B6C7F1@suse.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/4] PPC: e500: rename mpc8544ds
 into generic file
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Scott Wood <scottwood@freescale.com>, "qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>, =?ISO-8859-1?Q?Andreas_F=E4rb?= =?ISO-8859-1?Q?er?= <afaerber@suse.de>, qemu-devel qemu-devel <qemu-devel@nongnu.org>

Il 02/07/2012 23:17, Alexander Graf ha scritto:
>>> No, plain "e500.o" won't work no matter where you put it in the
>>> makefile (unless you add more global prefix setting).  I think
>>> he's suggesting that the plan is to eventually migrate to
>>> everything specifying its full path, though I don't see why.
> 
> Why wouldn't "e500.o" in hw/ppc/Makefile.objs work? I'd hope we
> traverse the target specific path first, no?

Not sure about the question... the idea is to abolish vpath and rely
only on the path to the current Makefile.objs file.

So, e500.o in hw/ppc/Makefile.objs, after the addsuffix would compile to
hw/ppc/e500.o

e500.o in hw/ppc/Makefile.objs, before the addsuffix would compile to
hw/ppc/../e500.o aka hw/e500.o

e500.o in hw/Makefile.objs would compile to hw/e500.o

There is no conflict between hw/e500.o and hw/ppc/e500.o, but of course
if you specify hw/e500.o twice (one normally, one via hw/ppc/..) you get
duplicate definitions.

Paolo