All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v3] qemu: fix out of tree cross compile
Date: Tue, 28 May 2013 11:21:17 +0200	[thread overview]
Message-ID: <51A4770D.5010006@redhat.com> (raw)
In-Reply-To: <51A474EC.6070604@suse.de>

Il 28/05/2013 11:12, Andreas Färber ha scritto:
> Am 28.05.2013 10:54, schrieb Paolo Bonzini:
>> Il 28/05/2013 01:49, Alexey Kardashevskiy ha scritto:
>>> The symlink to "asm" platform linux headers is made in the build tree by
>>> the configure script but gcc is not told to look for them there.
>>>
>>> The patch fixes this.
>>>
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>> ---
>>>
>>> The previous patch did not remove the old line adding includes. Early morning,
>>> lack of focus :)
>>>
>>> ---
>>>  configure |    2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> index 5ae7e4a..eca2a20 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -547,7 +547,7 @@ Haiku)
>>>    if [ "$cpu" = "i386" -o "$cpu" = "x86_64" ] ; then
>>>      audio_possible_drivers="$audio_possible_drivers fmod"
>>>    fi
>>> -  QEMU_INCLUDES="-I\$(SRC_PATH)/linux-headers $QEMU_INCLUDES"
>>> +  QEMU_INCLUDES="-I\$(SRC_PATH)/linux-headers -I$(pwd)/linux-headers $QEMU_INCLUDES"
>>>  ;;
>>>  esac
>>>  
>>>
>>
>> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> Hm, I see no other case of adding $(pwd) to QEMU_INCLUDES - shouldn't
> this just be -Ilinux-headers?

I think -Ilinux-headers would add
<builddir>/x86_64-softmmu/linux-headers, which is wrong.

> And might it make sense to give the build directory precedence over the
> source directory?

It shouldn't matter.

Paolo



WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v3] qemu: fix out of tree cross compile
Date: Tue, 28 May 2013 11:21:17 +0200	[thread overview]
Message-ID: <51A4770D.5010006@redhat.com> (raw)
In-Reply-To: <51A474EC.6070604@suse.de>

Il 28/05/2013 11:12, Andreas Färber ha scritto:
> Am 28.05.2013 10:54, schrieb Paolo Bonzini:
>> Il 28/05/2013 01:49, Alexey Kardashevskiy ha scritto:
>>> The symlink to "asm" platform linux headers is made in the build tree by
>>> the configure script but gcc is not told to look for them there.
>>>
>>> The patch fixes this.
>>>
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>> ---
>>>
>>> The previous patch did not remove the old line adding includes. Early morning,
>>> lack of focus :)
>>>
>>> ---
>>>  configure |    2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> index 5ae7e4a..eca2a20 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -547,7 +547,7 @@ Haiku)
>>>    if [ "$cpu" = "i386" -o "$cpu" = "x86_64" ] ; then
>>>      audio_possible_drivers="$audio_possible_drivers fmod"
>>>    fi
>>> -  QEMU_INCLUDES="-I\$(SRC_PATH)/linux-headers $QEMU_INCLUDES"
>>> +  QEMU_INCLUDES="-I\$(SRC_PATH)/linux-headers -I$(pwd)/linux-headers $QEMU_INCLUDES"
>>>  ;;
>>>  esac
>>>  
>>>
>>
>> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> Hm, I see no other case of adding $(pwd) to QEMU_INCLUDES - shouldn't
> this just be -Ilinux-headers?

I think -Ilinux-headers would add
<builddir>/x86_64-softmmu/linux-headers, which is wrong.

> And might it make sense to give the build directory precedence over the
> source directory?

It shouldn't matter.

Paolo

  reply	other threads:[~2013-05-28  9:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27  6:13 [Qemu-trivial] [PATCH] qemu: fix out of tree cross compile Alexey Kardashevskiy
2013-05-27  6:13 ` [Qemu-devel] " Alexey Kardashevskiy
2013-05-27 10:24 ` [Qemu-trivial] " Peter Maydell
2013-05-27 10:24   ` Peter Maydell
2013-05-27 14:11   ` [Qemu-trivial] " Alexey Kardashevskiy
2013-05-27 14:11     ` Alexey Kardashevskiy
2013-05-27 14:12     ` [Qemu-trivial] " Alexey Kardashevskiy
2013-05-27 14:12       ` [Qemu-devel] " Alexey Kardashevskiy
2013-05-27 15:02       ` [Qemu-trivial] " Paolo Bonzini
2013-05-27 15:02         ` [Qemu-devel] " Paolo Bonzini
2013-05-27 22:59         ` [Qemu-trivial] " Alexey Kardashevskiy
2013-05-27 22:59           ` [Qemu-devel] " Alexey Kardashevskiy
2013-05-27 23:44           ` [Qemu-trivial] [PATCH v2] " Alexey Kardashevskiy
2013-05-27 23:44             ` [Qemu-devel] " Alexey Kardashevskiy
2013-05-27 23:49             ` [Qemu-trivial] [PATCH v3] " Alexey Kardashevskiy
2013-05-27 23:49               ` [Qemu-devel] " Alexey Kardashevskiy
2013-05-28  8:54               ` [Qemu-trivial] " Paolo Bonzini
2013-05-28  8:54                 ` [Qemu-devel] " Paolo Bonzini
2013-05-28  9:12                 ` [Qemu-trivial] " Andreas Färber
2013-05-28  9:12                   ` Andreas Färber
2013-05-28  9:21                   ` Paolo Bonzini [this message]
2013-05-28  9:21                     ` Paolo Bonzini
2013-05-29 13:17               ` [Qemu-trivial] " Anthony Liguori
2013-05-29 13:17                 ` Anthony Liguori

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=51A4770D.5010006@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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.