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>,
John Stultz <john.stultz@linaro.org>,
Denys Dmytriyenko <denys@ti.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 1/1] selftests: timers: use LDLIBS instead of LDFLAGS to link against libpthread
Date: Wed, 28 Jun 2017 08:41:11 -0600 [thread overview]
Message-ID: <48527cb0-319e-a964-43cb-08f64f4aaefa@kernel.org> (raw)
In-Reply-To: <CAGNsrLBHcELzuxzxMqxYz6u2GSysDkzVk36p2Q7o6E8C+-ZvtA@mail.gmail.com>
On 06/28/2017 08:37 AM, Fathi Boudra wrote:
> On 28 June 2017 at 17:20, Shuah Khan <shuah@kernel.org> wrote:
>> On 06/28/2017 03:18 AM, Fathi Boudra wrote:
>>> timers test fails to build due to undefined reference:
>>>
>>> aarch64-linaro-linux-gcc --sysroot=/build/tmp-rpb-glibc/sysroots/hikey
>>> -O2 -pipe -g -feliminate-unused-debug-types -O3 -Wl,-no-as-needed -Wall
>>> -DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
>>> posix_timers.c
>>> -o /build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
>>> /tmp/cc1FTZzT.o: In function `check_timer_create':
>>> /usr/src/debug/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers.c:157:
>>> undefined reference to `timer_create'
>>> /usr/src/debug/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers.c:170:
>>> undefined reference to `timer_settime'
>>> collect2: error: ld returned 1 exit status
>>>
>>> Use LDLIBS instead of LDFLAGS to properly link against libpthread and fix
>>> this build issue.
>>>
>>> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
>>> Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
>>
>> I can't reproduce this on linux-kselftest next on x86_64. Is this arm64 speocific
>> problem? Please try this on linux-kselftest latest.
>
> yes, I tried linux-kselftest next and can reproduce.
> Maybe related to native build vs cross-build?
> I don't think it's arm64 specific.
>
Can you confirm that this change doesn't cause problems in native
build environments.
thanks,
-- Shuah
next prev parent reply other threads:[~2017-06-28 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 9:18 Fathi Boudra
2017-06-28 14:20 ` Shuah Khan
2017-06-28 14:37 ` Fathi Boudra
2017-06-28 14:41 ` Shuah Khan [this message]
2017-06-28 15:00 ` Fathi Boudra
2017-06-28 15:11 ` Shuah Khan
2017-06-28 15:56 ` Fathi Boudra
2017-06-28 16:04 ` Denys Dmytriyenko
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=48527cb0-319e-a964-43cb-08f64f4aaefa@kernel.org \
--to=shuah@kernel.org \
--cc=denys@ti.com \
--cc=fathi.boudra@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.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
all inboxes | Powered by JetHome®