mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: Re: linux/vt.h
Date: Sat, 3 Oct 2015 18:42:43 +0200	[thread overview]
Message-ID: <56100583.7090809@skarnet.org> (raw)
In-Reply-To: <CAKpSnp+jJvxm0yHCQKndk8nDDSg=xdRyxhT_y01JpZtH2JrTOQ@mail.gmail.com>

On 03/10/2015 15:01, Jorge Almeida wrote:
> Good question. Conventional wisdom states that one must keep the
> headers glibc was compiled against, not the headers of the current
> kernel, but the why is never explained.

  AIUI, it's a question of ABI. Your applications are linked against
the libc, not against the kernel: it's important for applications
and the libc to have the same definitions, else there's no guarantee
they'll work together. Whereas the kernel/userspace ABI is supposed
to be stable, so it's not supposed to matter if the current kernel
has different headers than the ones the libc was compiled against.
  Other people will correct me if I'm wrong.

-- 
  Laurent



  reply	other threads:[~2015-10-03 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03 12:27 linux/vt.h vlse
2015-10-03 13:01 ` linux/vt.h Jorge Almeida
2015-10-03 16:42   ` Laurent Bercot [this message]
2015-10-03 16:51     ` Jorge Almeida
2015-10-03 18:00   ` Rich Felker
2015-10-03 18:37     ` Jorge Almeida

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=56100583.7090809@skarnet.org \
    --to=ska-dietlibc@skarnet.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).