From: Florian Weimer <fweimer@redhat.com>
To: Michael Brunnbauer <brunni@netestate.de>
Cc: libc-help@sourceware.org
Subject: Re: 32bit glibc 2.30 and kernel 4.9.259: FATAL: kernel too old
Date: Thu, 04 Mar 2021 16:03:03 +0100 [thread overview]
Message-ID: <8735xbkllk.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <YEDv/NAM8fX/QSn9@netestate.de> (Michael Brunnbauer's message of "Thu, 4 Mar 2021 15:34:36 +0100")
* Michael Brunnbauer:
> I still have a 32bit glibc 2.30 lying around to run older programs that I
> did not get around to recompile. After upgrading from Kernel 4.9.255 to
> 4.9.259, they all fail with "FATAL: kernel too old". This seems to be a
> message from the loader.
>
> The suspicion offers itself that this is because the revision/patch number
> cannot be represented with a byte any more.
>
> Any idea what's going on and how to fix it?
How has this particular glibc been built?
Thanks,
Florian
next prev parent reply other threads:[~2021-03-04 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 14:34 Michael Brunnbauer
2021-03-04 15:03 ` Florian Weimer [this message]
2021-03-04 15:19 ` Michael Brunnbauer
2021-03-04 15:21 ` Florian Weimer
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=8735xbkllk.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--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).