From: Jason Yang <jasonyangshadow@gmail.com>
To: libc-alpha@sourceware.org
Subject: A question on glibc backwards compatibility
Date: Mon, 6 Jan 2020 11:59:32 +0900 [thread overview]
Message-ID: <2e35fa4e-7b88-ddeb-ddd4-bb87d9ad9ebb@gmail.com> (raw)
Dear Developers:
I knew that glibc has very good backwards compatibility. But I have an
issue during my development. I use very old glibc(version 2.5) to
compile my own developed dynamic library and use it on newer kernel,
some weird issues happen. Here, I could not explain these issues in
details because there are so much code involved. But my question is
that, glibc backwards compatibility is strict support? or if there are
any(few) exceptions? If there are exceptions where can I find them?
Sincerely looking forward to your response.
Regards
Jason
next reply other threads:[~2020-01-06 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 2:59 Jason Yang [this message]
2020-01-06 7:32 ` A question on glibc backwards compatibility Florian Weimer
[not found] ` <CAKCAbMi6cPXkNYZ13gOSW36qG-XziPBvJCqC=cstR8Ko9dbJLA@mail.gmail.com>
[not found] ` <61ae5450-a410-b438-9f7d-5dbd3bbc2838@gmail.com>
2020-01-06 22:43 ` Jason Yang
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=2e35fa4e-7b88-ddeb-ddd4-bb87d9ad9ebb@gmail.com \
--to=jasonyangshadow@gmail.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).