All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ltp-testsuite: Fix uClibc build with disabled fts.h support
Date: Mon, 22 Apr 2019 20:54:05 +0200	[thread overview]
Message-ID: <20190422205405.31c7ded0@windsurf> (raw)
In-Reply-To: <20190422172050.GA18445@dell5510>

On Mon, 22 Apr 2019 19:20:51 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:

> > And it builds perfectly fine.  
> Thanks for a research (I'll do more testing next time, not just reviewing)!
> Actually testing it, it's really ok, due these lines in
> package/ltp-testsuite/ltp-testsuite.mk:
> 
> # Requires uClibc fts and bessel support, normally not enabled
> ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
> define LTP_TESTSUITE_REMOVE_UNSUPPORTED
> 	rm -rf $(@D)/testcases/kernel/controllers/cpuset/
> 	rm -rf $(@D)/testcases/misc/math/float/bessel/
> 	rm -f $(@D)/testcases/misc/math/float/float_bessel.c
> endef
> LTP_TESTSUITE_POST_PATCH_HOOKS += LTP_TESTSUITE_REMOVE_UNSUPPORTED
> endif
> 
> We can either remove deleting testcases/kernel/controllers/cpuset/ as part of
> this patchset, or simply wait for next update (planning for the start of the
> second week in the May [1]), I'd remove it during the update.

Yes, let's wait for the new version of ltp-testsuite. The current
Buildroot package builds just fine with uClibc, I don't really see the
point of adding another ltp-testsuite patch at this point.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-04-22 18:54 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
2019-04-21 10:36 ` Thomas Petazzoni
2019-04-22 17:20   ` Petr Vorel
2019-04-22 18:54     ` Thomas Petazzoni [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=20190422205405.31c7ded0@windsurf \
    --to=thomas.petazzoni@bootlin.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.