All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bamvor Zhang Jian <bamvor.zhangjian@linaro.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	khilman@linaro.org, tyler.baker@linaro.org,
	shuahkh@osg.samsung.com
Subject: Re: [PATCH 2/7] selftests: add CFLAGS_EXTRA
Date: Tue, 25 Aug 2015 20:49:52 +0800	[thread overview]
Message-ID: <55DC6470.8030106@linaro.org> (raw)
In-Reply-To: <1440388080.9176.6.camel@ellerman.id.au>



On 08/24/2015 11:48 AM, Michael Ellerman wrote:
> On Fri, 2015-08-14 at 21:43 +0800, Bamvor Jian Zhang wrote:
>> One may pass the "-I /path/to/headers -L /path/to/lib" through
>> CFLAGS_EXTRA for cross compiling. mqueue could compile pass
>> in this way when we provide the popt.h and libpopt.so. And kdbus
>> could compile pass with sys/capability and libcap.so
> 
> There should be no need to define a new variable.
> 
> You should just update the relevant Makefiles to use CFLAGS += rather than
> CFLAGS =. And then you can just specifiy CFLAGS on the command line.
yeap, it works for me. There is only one line need to be changed:
diff --git a/tools/testing/selftests/mqueue/Makefile b/tools/testing/selftests/mqueue/Makefile
index 0e3b41e..ca8327f 100644
--- a/tools/testing/selftests/mqueue/Makefile
+++ b/tools/testing/selftests/mqueue/Makefile
@@ -1,4 +1,4 @@
-CFLAGS = -O2
+CFLAGS += -O2
 
 all:
 	$(CC) $(CFLAGS) mq_open_tests.c -o mq_open_tests -lrt

regards

bamvor
> 
> cheers
> 
> 

  reply	other threads:[~2015-08-25 12:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 13:43 [PATCH 0/7] Improvement kselftest support for arm and arm64 Bamvor Jian Zhang
2015-08-14 13:43 ` [PATCH 1/7] selftests: rename jump label to static_keys Bamvor Jian Zhang
2015-08-27 22:17   ` Shuah Khan
2015-09-07 10:33     ` Michael Ellerman
2015-09-08 13:03       ` Shuah Khan
2015-08-14 13:43 ` [PATCH 2/7] selftests: add CFLAGS_EXTRA Bamvor Jian Zhang
2015-08-24  3:48   ` Michael Ellerman
2015-08-25 12:49     ` Bamvor Zhang Jian [this message]
2015-08-27 10:23       ` Michael Ellerman
2015-08-14 13:43 ` [PATCH 3/7] selftests: exec: fix for running and installing Bamvor Jian Zhang
2015-08-27 10:55   ` Michael Ellerman
2015-08-14 13:43 ` [PATCH 4/7] selftests: check before install Bamvor Jian Zhang
2015-08-27 20:10   ` Shuah Khan
2015-08-27 22:13     ` Shuah Khan
2015-08-14 13:43 ` [PATCH 5/7] selftests: disable seccomp for arm64 Bamvor Jian Zhang
2015-08-24  3:48   ` Michael Ellerman
2015-08-25 12:51     ` Bamvor Zhang Jian
2015-08-14 13:43 ` [PATCH 6/7] selftests: only compile userfaultfd for x86 and powperpc Bamvor Jian Zhang
2015-08-27 22:20   ` Shuah Khan
2015-08-31  3:26   ` Michael Ellerman
2015-09-08  9:15     ` Bamvor Zhang Jian
2015-09-08  9:54       ` Michael Ellerman
2015-09-08 12:25         ` Bamvor Zhang Jian
2015-09-08 14:34           ` Andrea Arcangeli
2015-09-09  8:43             ` Michael Ellerman
2015-09-09 17:20               ` Andrea Arcangeli
2015-08-14 13:43 ` [PATCH 7/7] selftests: breakpoints: fix installing error on the architecture except x86 Bamvor Jian Zhang
2015-08-27 14:16   ` Shuah Khan
2015-08-27 22:14     ` Shuah Khan

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=55DC6470.8030106@linaro.org \
    --to=bamvor.zhangjian@linaro.org \
    --cc=broonie@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=shuahkh@osg.samsung.com \
    --cc=tyler.baker@linaro.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.