From: Shuah Khan <shuah@kernel.org>
To: Andy Lutomirski <luto@kernel.org>, Dmitry Safonov <dima@arista.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, X86 ML <x86@kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests/x86: Add <test_name>{,_32,_64} targets
Date: Thu, 18 Jan 2018 17:28:34 -0700 [thread overview]
Message-ID: <fb38bd16-9f95-d4ec-226d-925afd4e05ba@kernel.org> (raw)
In-Reply-To: <CALCETrX3gEQM+rMY4zY=D-K1xM2KM8jjMq4u=C5OxagjDAV9mQ@mail.gmail.com>
On 01/18/2018 04:10 PM, Andy Lutomirski wrote:
> On Thu, Jan 18, 2018 at 2:19 PM, Dmitry Safonov <dima@arista.com> wrote:
>> One can only use `make all` or `make <test_name>_<bitness>`
>> as make targets.
>> `make <test_name>` doesn't work as Ingo noticed:
>> x86> make test_vsyscall
>> gcc -O2 -g -std=gnu99 -pthread -Wall -no-pie test_vsyscall.c -o test_vsyscall
>> /tmp/aBaoo3nb.o: In function `init_vdso':
>> test_vsyscall.c:68: undefined reference to `dlopen'
>> test_vsyscall.c:76: undefined reference to `dlsym'
>> test_vsyscall.c:80: undefined reference to `dlsym'
>> test_vsyscall.c:84: undefined reference to `dlsym'
>> test_vsyscall.c:88: undefined reference to `dlsym'
>> test_vsyscall.c:70: undefined reference to `dlopen'
>> collect2: error: ld returned 1 exit status
>> <builtin>: recipe for target 'test_vsyscall' failed
>> make: *** [test_vsyscall] Error 1
>>
>> Makefile target substitution neither works :-/
>>
>> Generate .PHONY targets per-test and fix target substitution.
>
> Reviewed-by: Andy Lutomirski <luto@kernel.org>
>
>
Thanks for taking care of this. I plan to get this into 4.16-rc1
unless there is a dependency on x86 tree.
thanks,
-- Shuah
prev parent reply other threads:[~2018-01-19 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 22:19 Dmitry Safonov
2018-01-18 22:28 ` Dmitry Safonov
2018-01-18 23:10 ` Andy Lutomirski
2018-01-19 0:28 ` Shuah Khan [this message]
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=fb38bd16-9f95-d4ec-226d-925afd4e05ba@kernel.org \
--to=shuah@kernel.org \
--cc=dima@arista.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome