From: Letu Ren <fantasquex@gmail.com>
To: libc-help@sourceware.org
Subject: How to skip test when building glibc
Date: Sat, 11 Jun 2022 14:49:35 +0800 [thread overview]
Message-ID: <CAEUwDuDwiAgcOxcjW04OT-O7CmkdU4KBKKT5w0O6j2Q9gZsuig@mail.gmail.com> (raw)
Hi,
I want to build glibc on ArchLinux RISC-V, however, some unit tests
failure block my build script. I noticed that those failure also
appeared in official release notes of glibc v2.35. So, I think it's
safe to skip them. The problem is how to skip specific unit tests.
glibc uses autotools as the build system. However, I cannot find TESTS
and XFAIL_TESTS variables in Makefile. Glibc wiki of testsuite doesn't
mention it as well. I tried adding the XFAIL_TESTS variable to skip
tests, however, I failed. Could anyone help on this issue?
Letu Ren
next reply other threads:[~2022-06-11 6:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 6:49 Letu Ren [this message]
2022-06-14 23:15 ` Adhemerval Zanella
2022-06-15 11:48 ` Letu Ren
2022-06-15 12:11 ` Florian Weimer
2022-06-15 12:51 ` Letu Ren
2022-06-15 20:33 ` Adhemerval Zanella
2022-06-16 5:13 ` Letu Ren
2022-06-16 17:43 ` Adhemerval Zanella
2022-06-17 8:12 ` Letu Ren
2022-06-21 12:21 ` Adhemerval Zanella
2022-08-17 8:19 ` Letu Ren
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=CAEUwDuDwiAgcOxcjW04OT-O7CmkdU4KBKKT5w0O6j2Q9gZsuig@mail.gmail.com \
--to=fantasquex@gmail.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).