From: lei yang <lei.yang@windriver.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: <linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests: futex: fix compilation error
Date: Wed, 8 Nov 2017 15:55:02 +0800 [thread overview]
Message-ID: <f8400076-9971-8108-1d0d-25280a7025d3@windriver.com> (raw)
In-Reply-To: <3605f466-52f7-fdac-0d08-01361648b801@osg.samsung.com>
On 2017年11月08日 06:57, Shuah Khan wrote:
> On 11/06/2017 06:18 PM, lei yang wrote:
>>
>> On 2017年11月07日 07:48, Shuah Khan wrote:
>>> On 11/06/2017 04:45 PM, Shuah Khan wrote:
>>>> On 11/05/2017 09:03 PM, Lei Yang wrote:
>>>>> I run into below error when building futext
>>>>> /bin/sh: -c: line 5: syntax error: unexpected end of file
>>>>>
>>>>> the closing ";" and "\" are necessary.
>>>>> My OS is "Ubuntu 14.04.5 LTS"
>>>>>
>>>>> Signed-off-by: Lei Yang <Lei.Yang@windriver.com>
>>>>> ---
>>>>> tools/testing/selftests/futex/Makefile | 6 +++---
>>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>>
>>>>> diff --git a/tools/testing/selftests/futex/Makefile b/tools/testing/selftests/futex/Makefile
>>>>> index f0c0369..943f3a2 100644
>>>>> --- a/tools/testing/selftests/futex/Makefile
>>>>> +++ b/tools/testing/selftests/futex/Makefile
>>>>> @@ -11,9 +11,9 @@ all:
>>>>> BUILD_TARGET=$(OUTPUT)/$$DIR; \
>>>>> mkdir $$BUILD_TARGET -p; \
>>>>> make OUTPUT=$$BUILD_TARGET -C $$DIR $@;\
>>>>> - if [ -e $$DIR/$(TEST_PROGS) ]; then
>>>>> - rsync -a $$DIR/$(TEST_PROGS) $$BUILD_TARGET/;
>>>>> - fi
>>>>> + if [ -e $$DIR/$(TEST_PROGS) ]; then \
>>>>> + rsync -a $$DIR/$(TEST_PROGS) $$BUILD_TARGET/; \
>>>>> + fi \
>>>>> done
>>>>> override define RUN_TESTS
>>>>>
>>>> Hmm. I don't see this error on linux_4.14-rc8?
>>>>
>>>> Can you give more details on the gcc version you are using?
>>> I meant gnumake version? I am not seeing the failure with what I am
>>> using
>> $ make -v
>> GNU Make 3.81
>> Copyright (C) 2006 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.
>> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
>> PARTICULAR PURPOSE.
>>
>> This program built for x86_64-pc-linux-gnu
>>
>>
>> Lei
>>
> I can't take patches that aren't tested on the latest kernel release.
> 3.16 is very old. I am not going reply to other patches you sent.
>
> Please make sure the patches are based on the latest release and tested
> on it as well.
this error only happens when use old version "make", it has nothing to
do with the new or old kernel.
so the question is do we need to be compatible with old "make" ?
Lei
>
> thanks,
> -- Shuah
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-08 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 4:03 Lei Yang
2017-11-06 23:45 ` Shuah Khan
2017-11-06 23:48 ` Shuah Khan
2017-11-07 1:18 ` lei yang
2017-11-07 22:57 ` Shuah Khan
2017-11-08 7:55 ` lei yang [this message]
2017-11-08 15:31 ` Shuah Khan
2017-11-07 1:17 ` lei yang
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=f8400076-9971-8108-1d0d-25280a7025d3@windriver.com \
--to=lei.yang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
/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
all inboxes | Powered by JetHome®