qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
	qemu-devel@nongnu.org, Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] build: Cleanup qga make output
Date: Mon, 12 Dec 2011 17:38:36 -0600	[thread overview]
Message-ID: <4EE6907C.3010901@linux.vnet.ibm.com> (raw)
In-Reply-To: <4EE68846.4010101@us.ibm.com>

On 12/12/2011 05:03 PM, Anthony Liguori wrote:
> On 12/07/2011 10:33 AM, Adam Litke wrote:
>> Currently the make variable qapi-dir refers to the qapi-generated
>> directory in
>> absolute terms. This causes the harmless but ugly make output below. By
>> changing this variable to the relative path the output conforms to the
>> norm and
>> the build works fine.
>>
>> Before patch:
>> CC /home/aglitke/src/qemu/qapi-generated/qga-qapi-types.o
>> CC /home/aglitke/src/qemu/qapi-generated/qga-qapi-visit.o
>> CC /home/aglitke/src/qemu/qapi-generated/qga-qmp-marshal.o
>> After patch:
>> CC qapi-generated/qga-qapi-types.o
>> CC qapi-generated/qga-qapi-visit.o
>> CC qapi-generated/qga-qmp-marshal.o
>
> This was supposedly to fix a build issue that I was never able to
> reproduce. I think Luiz could reproduce it though. Luiz, could you try
> out Adam's patch and confirm it breaks for you?

I think that was Stefano:

http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg02752.html

Stefano had a patch that fixed a build breakage he saw with dirty 
directories by setting:

qapi-dir := $(SRC_DIR)/qapi-generated

That patch ended up breaking the build for others, however, and was 
reverted.

This patch was an improvement on the original, but we'd all agreed that 
it wasn't necessary since we don't support working around issues related 
to dirty directories.

So if it's ugly, we can safely drop it.

>
> Regards,
>
> Anthony Liguori
>
>>
>> Signed-off-by: Adam Litke<agl@us.ibm.com>
>> ---
>> Makefile | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index 301c75e..7c93739 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -168,7 +168,7 @@ check-qjson: check-qjson.o $(qobject-obj-y)
>> $(tools-obj-y)
>> test-coroutine: test-coroutine.o qemu-timer-common.o async.o
>> $(coroutine-obj-y) $(tools-obj-y)
>>
>> $(qapi-obj-y): $(GENERATED_HEADERS)
>> -qapi-dir := $(BUILD_DIR)/qapi-generated
>> +qapi-dir := qapi-generated
>> test-visitor.o test-qmp-commands.o qemu-ga$(EXESUF): QEMU_CFLAGS += -I
>> $(qapi-dir)
>> qemu-ga$(EXESUF): LIBS = $(LIBS_QGA)
>>
>
>

  reply	other threads:[~2011-12-12 23:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 16:33 [Qemu-devel] [PATCH] build: Cleanup qga make output Adam Litke
2011-12-12 23:03 ` Anthony Liguori
2011-12-12 23:38   ` Michael Roth [this message]
2011-12-13 12:23     ` Luiz Capitulino
2011-12-13 14:33       ` Adam Litke
2011-12-13 15:22         ` Michael Roth
2011-12-13 18:33           ` Luiz Capitulino

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=4EE6907C.3010901@linux.vnet.ibm.com \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=agl@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=lcapitulino@redhat.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).