All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Scott Wood" <scottwood@freescale.com>,
	"qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"qemu-devel qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/4] PPC: e500: rename mpc8544ds into generic file
Date: Tue, 03 Jul 2012 13:33:29 +0200	[thread overview]
Message-ID: <4FF2D889.4090306@redhat.com> (raw)
In-Reply-To: <17B4AA66-74DA-47D6-BB0B-12EA67B6C7F1@suse.de>

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

      parent reply	other threads:[~2012-07-03 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120627235055.GA9149@tyr.buserror.net>
2012-07-02 16:50 ` [Qemu-devel] [PATCH 1/4] PPC: e500: rename mpc8544ds into generic file Andreas Färber
2012-07-02 17:06   ` Scott Wood
2012-07-02 20:32     ` [Qemu-devel] [Qemu-ppc] " Scott Wood
2012-07-02 20:58       ` Andreas Färber
2012-07-02 21:07         ` Scott Wood
2012-07-02 21:08           ` Alexander Graf
2012-07-02 21:16             ` Scott Wood
2012-07-02 21:17               ` Alexander Graf
2012-07-02 21:28                 ` Scott Wood
2012-07-03 11:33                 ` 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=4FF2D889.4090306@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.com \
    /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.