From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v3] qemu: fix out of tree cross compile
Date: Tue, 28 May 2013 11:12:12 +0200 [thread overview]
Message-ID: <51A474EC.6070604@suse.de> (raw)
In-Reply-To: <51A470A9.8000502@redhat.com>
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?
And might it make sense to give the build directory precedence over the
source directory?
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-28 9:12 UTC|newest]
Thread overview: 12+ 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 10:24 ` [Qemu-trivial] [Qemu-devel] " Peter Maydell
2013-05-27 14:11 ` Alexey Kardashevskiy
2013-05-27 14:12 ` [Qemu-trivial] " Alexey Kardashevskiy
2013-05-27 15:02 ` Paolo Bonzini
2013-05-27 22:59 ` Alexey Kardashevskiy
2013-05-27 23:44 ` [Qemu-trivial] [PATCH v2] " Alexey Kardashevskiy
2013-05-27 23:49 ` [Qemu-trivial] [PATCH v3] " Alexey Kardashevskiy
2013-05-28 8:54 ` Paolo Bonzini
2013-05-28 9:12 ` Andreas Färber [this message]
2013-05-28 9:21 ` [Qemu-trivial] [Qemu-devel] " Paolo Bonzini
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=51A474EC.6070604@suse.de \
--to=afaerber@suse.de \
--cc=aik@ozlabs.ru \
--cc=pbonzini@redhat.com \
--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 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).