From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ltp-testsuite: Fix uClibc build with disabled fts.h support
Date: Thu, 18 Apr 2019 00:55:39 +0200 [thread overview]
Message-ID: <20190417225537.GB27193@x230> (raw)
In-Reply-To: <20190417135458.15505-1-Nikita.Sobolev@synopsys.com>
Hi Nikita,
> Add patch, that fixes build on uClibc with disabled fts.h support
> and MUSL, which does not have fts.h at all.
Due autotools macros changes, which requires running autoreconf you need to add
into package/ltp-testsuite/ltp-testsuite.mk:
# Required by patch 0002-cpuset-Detect-missing-fts.h.patch
LTP_TESTSUITE_AUTORECONF = YES
FYI: while my patch in LTP upstream fixes uClibc with disabled fts.h, it's not
enough for MUSL build, which is disabled. I've sent some experimental support to
buildroot ML last month [2] (backported some fixes + simply delete the rest of
problematic tests), but due either my problems with patchwork or outdated
patchwork instance on ozlabs it didn't arrive to buildroot patchwork.
And I don't know whether buildroot uses (or allows user) to disable
UCLIBC_HAS_FTS (whether this patch is actually useful).
> Original patch [1] will be a part of the next LTP release and
> current patch should be removed from Buildroot when LTP version
> is bumped.
NOTE: we're planning next release in about 2 weeks, I usually update package the
same day.
> [1] https://github.com/linux-test-project/ltp/commit/b24f3d32c54006af5499da5a7ac418eafcf6e459
> Signed-off-by: Nikita Sobolev <Nikita.Sobolev@synopsys.com>
Acked-by: Petr Vorel <petr.vorel@gmail.com>
(with LTP_TESTSUITE_AUTORECONF = yes)
Kind regards,
Petr
[2] http://lists.busybox.net/pipermail/buildroot/2019-March/thread.html
next prev parent reply other threads:[~2019-04-17 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 13:54 [Buildroot] [PATCH] ltp-testsuite: Fix uClibc build with disabled fts.h support Nikita Sobolev
2019-04-17 13:57 ` Thomas Petazzoni
2019-04-17 22:55 ` Petr Vorel [this message]
2019-04-21 10:36 ` Thomas Petazzoni
2019-04-22 17:20 ` Petr Vorel
2019-04-22 18:54 ` Thomas Petazzoni
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=20190417225537.GB27193@x230 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.