From: Shuah Khan <shuah@kernel.org>
To: Fathi Boudra <fathi.boudra@linaro.org>
Cc: linux-kselftest@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
SeongJae Park <sj38.park@gmail.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests: net: use LDLIBS instead of LDFLAGS to link against libnuma
Date: Wed, 28 Jun 2017 09:12:19 -0600 [thread overview]
Message-ID: <1039eb4d-76a2-432f-f3d5-06fd8a5b66af@kernel.org> (raw)
In-Reply-To: <CAGNsrLDygrxzFwCUEddv0+1O=zfPuKRxzhujoQk0SLRDPqEV8g@mail.gmail.com>
On 06/28/2017 08:36 AM, Fathi Boudra wrote:
> On 28 June 2017 at 17:19, Shuah Khan <shuah@kernel.org> wrote:
>> On 06/28/2017 05:19 AM, Fathi Boudra wrote:
>>> reuseport_bpf_numa fails to build with undefined reference:
>>>
>>> aarch64-linaro-linux-gcc
>>> --sysroot=/build/tmp-rpb-glibc/sysroots/hikey -Wall
>>> -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -Wl,-O1
>>> -Wl,--hash-style=gnu -Wl,--as-needed -lnuma reuseport_bpf_numa.c
>>> -o
>>> /build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/net/reuseport_bpf_numa
>>> /tmp/ccfUuExT.o: In function `send_from_node':
>>> /build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/net/reuseport_bpf_numa.c:138:
>>> undefined reference to `numa_run_on_node'
>>> /tmp/ccfUuExT.o: In function `main':
>>> /build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/net/reuseport_bpf_numa.c:230:
>>> undefined reference to `numa_available'
>>> /build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/net/reuseport_bpf_numa.c:233:
>>> undefined reference to `numa_max_node'
>>>
>>> Use LDLIBS instead of LDFLAGS to properly link against libnuma.
>>>
>>> Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
>>
>> Did you try this on linux-ksefltest next? It has the fix for this.
>
> yes, I tried linux-ksefltest next and can reproduce.
My question is whether this fix is on top of linux-kselftest next.
>
>> thanks,
>> -- Shuah
>>> ---
>>> tools/testing/selftests/net/Makefile | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/tools/testing/selftests/net/Makefile b/tools/testing/selftests/net/Makefile
>>> index 35cbb4cba410..17c732a19c4c 100644
>>> --- a/tools/testing/selftests/net/Makefile
>>> +++ b/tools/testing/selftests/net/Makefile
>>> @@ -3,7 +3,7 @@
>>> CFLAGS = -Wall -Wl,--no-as-needed -O2 -g
>>> CFLAGS += -I../../../../usr/include/
>>>
>>> -reuseport_bpf_numa: LDFLAGS += -lnuma
>>> +reuseport_bpf_numa: LDLIBS += -lnum
>>>
>>> TEST_PROGS := run_netsocktests run_afpackettests test_bpf.sh netdevice.sh
>>> TEST_GEN_FILES = socket
>
Please redo the patch on top of
SeongJae Park's fix
selftest/net/Makefile: Specify output with $(OUTPUT)
btw - with the the above fix, I don't see any failures on x86_64.
I am curious why it fails in cross-build? Could you figure out if
your cross-build environment is good.
thanks,
-- Shuah
prev parent reply other threads:[~2017-06-28 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 11:19 Fathi Boudra
2017-06-28 14:19 ` Shuah Khan
2017-06-28 14:36 ` Fathi Boudra
2017-06-28 15:12 ` 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=1039eb4d-76a2-432f-f3d5-06fd8a5b66af@kernel.org \
--to=shuah@kernel.org \
--cc=fathi.boudra@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sj38.park@gmail.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®