From: Manolis Ragkousis <manolis837@gmail.com>
To: guix-devel@gnu.org
Subject: [PATCH] gnu: glibc/linux: Rename linux-headers input to kernel-headers.
Date: Thu, 4 Feb 2016 16:23:42 +0200 [thread overview]
Message-ID: <56B35EEE.2060207@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
Hello everyone,
This patch applies to wip-hurd. In order to use it on master, the (gnu
packages commencement) module should also be modified, which is already
the case in wip-hurd.
I will push the patch to wip-hurd.
Manolis
[-- Attachment #2: 0001-gnu-glibc-linux-Rename-linux-headers-input-to-kernel.patch --]
[-- Type: text/x-patch, Size: 1306 bytes --]
From 846930e55796b04b00d61c3d9c15546c978a0af0 Mon Sep 17 00:00:00 2001
From: Manolis Ragkousis <manolis837@gmail.com>
Date: Thu, 4 Feb 2016 15:50:19 +0200
Subject: [PATCH] gnu: glibc/linux: Rename linux-headers input to
kernel-headers.
* gnu/packages/base.scm (glibc/linux)[propagated-inputs]: Use a kernel
agnostic name for the kernel headers.
---
gnu/packages/base.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
index 4373716..547753d 100644
--- a/gnu/packages/base.scm
+++ b/gnu/packages/base.scm
@@ -493,7 +493,7 @@ store.")
;; Glibc's <limits.h> refers to <linux/limit.h>, for instance, so glibc
;; users should automatically pull Linux headers as well.
- (propagated-inputs `(("linux-headers" ,linux-libre-headers)))
+ (propagated-inputs `(("kernel-headers" ,linux-libre-headers)))
(outputs '("out" "debug"))
@@ -533,7 +533,7 @@ store.")
,version)
(string-append "--with-headers="
- (assoc-ref %build-inputs "linux-headers")
+ (assoc-ref %build-inputs "kernel-headers")
"/include")
;; This is the default for most architectures as of GNU libc 2.21,
--
2.7.0
next reply other threads:[~2016-02-04 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:23 Manolis Ragkousis [this message]
2016-02-04 21:36 ` [PATCH] gnu: glibc/linux: Rename linux-headers input to kernel-headers Ludovic Courtès
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=56B35EEE.2060207@gmail.com \
--to=manolis837@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.