From: Shuah Khan <skhan@linuxfoundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kselftest <linux-kselftest@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
paulmck <paulmck@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
"skh >> Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/rseq: Fix out-of-tree compilation
Date: Thu, 20 Feb 2020 09:17:50 -0700 [thread overview]
Message-ID: <5c55d7c0-ba0c-8bb8-60c0-203dfaaf1d2b@linuxfoundation.org> (raw)
In-Reply-To: <763647628.2256.1582215383750.JavaMail.zimbra@efficios.com>
On 2/20/20 9:16 AM, Mathieu Desnoyers wrote:
> ----- On Feb 20, 2020, at 6:37 AM, Michael Ellerman mpe@ellerman.id.au wrote:
>
>> Currently if you build with O=... the rseq tests don't build:
>>
>> $ make O=$PWD/output -C tools/testing/selftests/ TARGETS=rseq
>> make: Entering directory '/linux/tools/testing/selftests'
>> ...
>> make[1]: Entering directory '/linux/tools/testing/selftests/rseq'
>> gcc -O2 -Wall -g -I./ -I../../../../usr/include/ -L./ -Wl,-rpath=./ -shared
>> -fPIC rseq.c -lpthread -o /linux/output/rseq/librseq.so
>> gcc -O2 -Wall -g -I./ -I../../../../usr/include/ -L./ -Wl,-rpath=./
>> basic_test.c -lpthread -lrseq -o /linux/output/rseq/basic_test
>> /usr/bin/ld: cannot find -lrseq
>> collect2: error: ld returned 1 exit status
>>
>> This is because the library search path points to the source
>> directory, not the output.
>>
>> We can fix it by changing the library search path to $(OUTPUT).
>
> Good catch!
>
> Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>
> Shuah, can you pick this up please ?
>
I applied it to linux-kselftest fixes just a little while ago.
I will send this in for rc4.
thanks,
-- Shuah
prev parent reply other threads:[~2020-02-20 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 11:37 [PATCH] selftests/rseq: Fix out-of-tree compilation Michael Ellerman
2020-02-20 16:16 ` Mathieu Desnoyers
2020-02-20 16:17 ` 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=5c55d7c0-ba0c-8bb8-60c0-203dfaaf1d2b@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mpe@ellerman.id.au \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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