From: Vineet Gupta <vineet.gupta1@synopsys.com>
To: <libc-alpha@sourceware.org>
Subject: misc/check-installed-headers-c failing due to upstream kernel change
Date: Mon, 21 Jan 2019 14:56:49 -0800 [thread overview]
Message-ID: <4db851ae-9bb2-2159-96bf-c4b34b505bd9@synopsys.com> (raw)
Hi,
It seems a recent upstream kernel change (went in 5.0-rcX) 81c9d43f9487
("kernel/sysctl: add panic_print into sysctl") trips one of the glibc tests.
FAIL: misc/check-installed-headers-c
| :: sys/sysctl.h
| ::::
| *** Obsolete types detected:
| ~/install/compilers/arc-linux-gnu/sysroot/usr/include/linux /sysctl.h:
| KERN_PANIC_PRINT=78, /* ulong: bitmask to print system info on panic */
It doesn't seem to like ulong (inside a comment). I don't have enough foo to fix
it, but wanted to bring it to notice anyways.
Thx,
-Vineet
next reply other threads:[~2019-01-21 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 22:56 Vineet Gupta [this message]
2019-01-23 15:57 ` misc/check-installed-headers-c failing due to upstream kernel change Ben Hutchings
2019-01-23 16:51 ` Carlos O'Donell
2019-01-23 17:13 ` Vineet Gupta
2019-01-23 17:24 ` Carlos O'Donell
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4db851ae-9bb2-2159-96bf-c4b34b505bd9@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=libc-alpha@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).