From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Michael Brunnbauer <brunni@netestate.de>, libc-help@sourceware.org
Subject: Re: glibc 2.36 make check
Date: Thu, 4 Aug 2022 11:37:18 -0300 [thread overview]
Message-ID: <0b3f2805-ff48-b109-d3b5-d9e3debb2791@linaro.org> (raw)
In-Reply-To: <YupuKnSPhDv5uifN@netestate.de>
On 03/08/22 09:46, Michael Brunnbauer wrote:
>
> hi all,
>
> make check with the new version of glibc has two new failures on my custom
> system:
>
> FAIL: misc/tst-mount-consts
>
> From misc/tst-mount-consts.out:
>
> test.c:2:10: fatal error: linux/mount.h: No such file or directory
> #include <linux/mount.h>
>
> /usr/include/linux/mount.h is indeed missing and I checked that
> make headers_install with my current kernel would not change that.
The header was added only at 5.0 version, we will need to set the test unsupported
if the headers is not present.
>
> FAIL: nptl/tst-pthread-gdb-attach-static
>
> I have attached the file nptl/tst-pthread-gdb-attach-static.out.
This is unexpected, although the log is not clear. I am not sure sure if this is
gdb issue in fact.
>
> Should I worry about those new failed tests?
>
> Here is some data about my setup:
>
> -glibc configure options:
> --prefix=/usr --enable-kernel=4.9.0 --host=x86_64-pc-linux-gnu --disable-experimental-malloc
> -kernel version: 4.9.320
> -installed kernel headers: from some older 4.9.x kernel
> -gcc version: 7.5.0
> -gdb version 9.1
>
> Regards,
>
> Michael Brunnbauer
>
prev parent reply other threads:[~2022-08-04 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 12:46 Michael Brunnbauer
2022-08-04 14:37 ` Adhemerval Zanella Netto [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=0b3f2805-ff48-b109-d3b5-d9e3debb2791@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=brunni@netestate.de \
--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).