From: Khem Raj <raj.khem@gmail.com>
To: Petr Vorel <petr.vorel@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 1/2] ltp: Update to 20200120
Date: Sat, 29 Feb 2020 07:12:05 -0800 [thread overview]
Message-ID: <0147f807-be3c-27e0-e05c-73ac0311045e@gmail.com> (raw)
In-Reply-To: <20200229064656.GA4045619@x230>
On 2/28/20 10:46 PM, Petr Vorel wrote:
> Hi Richard, Khem,
>
>>> Changes v4->v5:
>>> * Put back 0002-kernel-controllers-Link-with-libfts-explicitly-on-
>>> mu.patch
>>> as it still needed on MUSL (although it should not be needed,
>>> strange).
>>> Reported by Anuj Mittal
>
>> I'm sorry to say that this still isn't quite right for musl:
>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/1634
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/1630
>
>> Still having the fts issue :(
> OK, step1b is still problematic:
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/ltp/20200120-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux-musl/../../libexec/x86_64-poky-linux-musl/gcc/x86_64-poky-linux-musl/9.2.0/ld: /usr/src/debug/ltp/20200120-r0/git/testcases/kernel/controllers/cpuset/cpuset_lib/libcpuset.c:3224: undefined reference to `fts_read'
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/ltp/20200120-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux-musl/../../libexec/x86_64-poky-linux-musl/gcc/x86_64-poky-linux-musl/9.2.0/ld: /usr/src/debug/ltp/20200120-r0/git/testcases/kernel/controllers/cpuset/cpuset_lib/libcpuset.c:3224: undefined reference to `fts_read'
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/ltp/20200120-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux-musl/../../libexec/x86_64-poky-linux-musl/gcc/x86_64-poky-linux-musl/9.2.0/ld: /usr/src/debug/ltp/20200120-r0/git/testcases/kernel/controllers/cpuset/cpuset_lib/libcpuset.c:3269: undefined reference to `fts_close'
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/ltp/20200120-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux-musl/../../libexec/x86_64-poky-linux-musl/gcc/x86_64-poky-linux-musl/9.2.0/ld: /usr/src/debug/ltp/20200120-r0/git/testcases/kernel/controllers/cpuset/cpuset_lib/libcpuset.c:3277: undefined reference to `fts_close'
>
> At least we know, that once we solve this problem, we can remove
> 0002-kernel-controllers-Link-with-libfts-explicitly-on-mu.patch
>
> Please, how to reproduce this build locally? Is it:
> . oe-init-build-env
> TCLIBC=musl bitbake ltp
>
> Or do I need to put something into config files conf/local.conf
> or conf/bblayers.conf ?
>
> I need to double check if musl-fts is really built and whether the order of
> -lfts is correct. But all this has been solved even for static build for Buildroot,
> so I guess it's some issue related to openembedded. Unfortunately, I'm not much
> experienced in openembedded (stepped in, because nobody else has updated LTP
> package yet).
>
> Khem, any idea, what can be wrong?
I have added -lfts to LIBS and sent v6 of this patch
>
> Kind regards,
> Petr
>
prev parent reply other threads:[~2020-02-29 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 17:57 [PATCH v5 1/2] ltp: Update to 20200120 Petr Vorel
2020-02-28 17:57 ` [PATCH v5 2/2] ltp: Remove mips related open_posix_testsuite patch Petr Vorel
2020-02-28 23:02 ` [PATCH v5 1/2] ltp: Update to 20200120 Richard Purdie
2020-02-29 6:46 ` Petr Vorel
2020-02-29 13:22 ` Richard Purdie
2020-02-29 13:42 ` Richard Purdie
2020-02-29 13:53 ` Richard Purdie
2020-02-29 15:13 ` Khem Raj
2020-02-29 17:00 ` Petr Vorel
2020-02-29 18:40 ` Petr Vorel
2020-02-29 20:44 ` Khem Raj
2020-02-29 15:12 ` Khem Raj [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=0147f807-be3c-27e0-e05c-73ac0311045e@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=petr.vorel@gmail.com \
--cc=richard.purdie@linuxfoundation.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