From: Philip McGrath <philip@philipmcgrath.com>
To: Maxime Devos <maximedevos@telenet.be>, 55998@debbugs.gnu.org
Subject: [bug#55998] [PATCH] gnu: Add cctools.
Date: Wed, 15 Jun 2022 15:34:53 -0400 [thread overview]
Message-ID: <9d532cc8-a87b-1ccd-a90b-5c14eca19254@philipmcgrath.com> (raw)
In-Reply-To: <6213c4a5a183b3ed1428937d576fed8f2fa1ce9f.camel@telenet.be>
On 6/15/22 14:55, Maxime Devos wrote:
> Philip McGrath schreef op wo 15-06-2022 om 13:15 [-0400]:
>> + ;; FIXME: This is a very ugly way to make
>> + ;; #include <linux/limits.h>
>> + ;; work---what is a better way?
>
>
> Searching for <linux/limit.h> in the guix git checkout, I found:
>
> ;; Glibc's <limits.h> refers to <linux/limit.h>, for instance, so glibc
> ;; users should automatically pull Linux headers as well. On GNU/Hurd,
> ;; libc provides <hurd.h>, which includes a bunch of Hurd and Mach headers,
> ;; so both should be propagated.
> (propagated-inputs
> (if (hurd-target?)
> `(("hurd-core-headers" ,hurd-core-headers))
> `(("kernel-headers" ,linux-libre-headers))))
>
> (The hurd bit is not relevant here, and in this case I'd assume that no
> propagation is required.)
>
I saw that, too, and I don't understand why <linux/limits.h> (it's
plural) isn't found automatically, especially when the neighboring
<limits.h> is found: with both clang-toolchain and gcc-toolchain,
include/linux is a symlink into linux-libre-headers.
-Philip
next prev parent reply other threads:[~2022-06-15 19:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 17:15 [bug#55998] [PATCH] gnu: Add cctools Philip McGrath
2022-06-15 18:32 ` Maxime Devos
2022-06-15 18:45 ` Maxime Devos
2022-06-15 19:06 ` Philip McGrath
2022-06-15 19:35 ` Maxime Devos
2022-06-15 21:00 ` Philip McGrath
2022-06-15 21:11 ` Maxime Devos
2022-06-15 21:20 ` ( via Guix-patches via
2022-06-15 18:53 ` Maxime Devos
2022-06-15 19:19 ` Philip McGrath
2022-06-15 20:07 ` Maxime Devos
2022-06-17 11:28 ` Philip McGrath
2022-06-15 18:55 ` Maxime Devos
2022-06-15 19:34 ` Philip McGrath [this message]
2022-06-15 18:56 ` Maxime Devos
2022-06-15 19:21 ` Philip McGrath
2022-06-15 19:23 ` Maxime Devos
2022-06-17 11:19 ` Philip McGrath
2022-06-15 20:04 ` Maxime Devos
2022-06-17 11:09 ` Philip McGrath
2022-06-19 21:01 ` Ludovic Courtès
2022-06-15 20:17 ` Maxime Devos
2022-06-16 22:29 ` Philip McGrath
2022-06-17 6:14 ` Maxime Devos
2022-06-15 20:18 ` Maxime Devos
2022-06-15 20:23 ` Maxime Devos
2022-06-16 23:29 ` Philip McGrath
2022-06-17 11:51 ` [bug#55998] [PATCH v2] " Philip McGrath
2022-06-19 21:02 ` bug#55998: [PATCH] " 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d532cc8-a87b-1ccd-a90b-5c14eca19254@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=55998@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.savannah.gnu.org/cgit/guix.git
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).