public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Mark Wielaard <mark@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] INSTALL: regenerate Date: Tue, 9 Jan 2024 13:56:10 +0000 (GMT) [thread overview] Message-ID: <20240109135610.EF8CB3857839@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3265f934368554cc629ca38b3b5311796c06945c commit 3265f934368554cc629ca38b3b5311796c06945c Author: Mark Wielaard <mark@klomp.org> Date: Tue Jan 9 01:15:15 2024 +0100 INSTALL: regenerate Diff: --- INSTALL | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/INSTALL b/INSTALL index ee5b74e659..ef52d749ff 100644 --- a/INSTALL +++ b/INSTALL @@ -609,13 +609,13 @@ Specific advice for GNU/Linux systems If you are installing the GNU C Library on GNU/Linux systems, you need to have the header files from a 3.2 or newer kernel around for -reference. These headers must be installed using ‘make headers_install’; -the headers present in the kernel source directory are not suitable for -direct use by the GNU C Library. You do not need to use that kernel, -just have its headers installed where the GNU C Library can access them, -referred to here as INSTALL-DIRECTORY. The easiest way to do this is to -unpack it in a directory such as ‘/usr/src/linux-VERSION’. In that -directory, run ‘make headers_install +reference. These headers must be installed using ‘make +headers_install’; the headers present in the kernel source directory are +not suitable for direct use by the GNU C Library. You do not need to +use that kernel, just have its headers installed where the GNU C Library +can access them, referred to here as INSTALL-DIRECTORY. The easiest way +to do this is to unpack it in a directory such as +‘/usr/src/linux-VERSION’. In that directory, run ‘make headers_install INSTALL_HDR_PATH=INSTALL-DIRECTORY’. Finally, configure the GNU C Library with the option ‘--with-headers=INSTALL-DIRECTORY/include’. Use the most recent kernel you can get your hands on. (If you are
next reply other threads:[~2024-01-09 13:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-09 13:56 Mark Wielaard [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-07-30 19:19 Andreas K. Huttel
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=20240109135610.EF8CB3857839@sourceware.org \ --to=mark@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).