qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dave Martin <Dave.Martin@arm.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [RISU PATCH 06/10] configure: support CPPFLAGS
Date: Wed, 08 Nov 2017 11:02:50 +0000	[thread overview]
Message-ID: <87lgjhqbhh.fsf@linaro.org> (raw)
In-Reply-To: <20171108103416.GA8971@e103592.cambridge.arm.com>


Dave Martin <Dave.Martin@arm.com> writes:

> On Tue, Nov 07, 2017 at 03:05:54PM +0000, Alex Bennée wrote:
>> Useful for accessing API's that are still brewing, e.g:
>>
>>   CROSS_PREFIX=aarch64-linux-gnu- \
>>     CPPFLAGS=-I/home/alex/lsrc/qemu/risu.git/sve-headers/include \
>>     ../configure
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>>  README    | 6 ++++++
>>  configure | 1 +
>>  2 files changed, 7 insertions(+)
>>
>> diff --git a/README b/README
>> index 9946e6e..fbe408d 100644
>> --- a/README
>> +++ b/README
>> @@ -26,6 +26,12 @@ Most useful is
>>     need this if you're not building on the target system
>>     (Example: CROSS_PREFIX=arm-linux-gnueabihf- )
>>
>> +Another useful flag is
>> + CPPFLAGS= which specified pre-processor flags, usually -I statements
>> +   for specifying extra include paths. Use this is you need something
>
> s/is/if/
>
>> +   from new kernel headers not installed on your system.
>> +   (Example: CPPFLAGS=-I/path/to/sve-kernel-headers/include)
>> +
>
> You should probably point out that the path should refer to headers
> installed by running 'make headers_install' in the Linux source.  This
> means we really test the uapi headers properly, and I don't get spurious
> bug reports about bad headers ;)

Will do. Thanks.
>
> [...]
>
> Cheers
> ---Dave


--
Alex Bennée

  reply	other threads:[~2017-11-08 11:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 15:05 [Qemu-devel] [RISU PATCH 00/10] Initial support for SVE Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 01/10] build-all-arches: drop -t (for tty) from docker invocation Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 02/10] risu.c: split out setting up options Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 03/10] risu.c: add missing --trace longopt Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 04/10] risu: move optional args to each architecture Alex Bennée
2017-11-09  8:13   ` Richard Henderson
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 05/10] configure: allow repeated invocation of configure in build dir Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 06/10] configure: support CPPFLAGS Alex Bennée
2017-11-08 10:34   ` Dave Martin
2017-11-08 11:02     ` Alex Bennée [this message]
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 07/10] risugen: add --sve support Alex Bennée
2017-11-09  8:18   ` Richard Henderson
2017-11-09 12:21   ` Dave Martin
2017-11-09 14:50     ` Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 08/10] aarch64.risu: initial SVE instruction Alex Bennée
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 09/10] risu_reginfo_aarch64: add reginfo_copy_sve Alex Bennée
2017-11-08 10:46   ` Dave Martin
2017-11-07 15:05 ` [Qemu-devel] [RISU PATCH 10/10] risu_reginfo_aarch64: add SVE support to reginfo_dump_mismatch Alex Bennée
2017-11-08 10:58   ` Dave Martin
2017-11-08 11:41     ` Alex Bennée
2017-11-08 10:36 ` [Qemu-devel] [RISU PATCH 00/10] Initial support for SVE Dave Martin
2017-11-08 11:02   ` Alex Bennée
2017-11-08 11:12     ` Dave Martin
2017-11-21 16:51 ` Peter Maydell

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=87lgjhqbhh.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Dave.Martin@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).