From: Nikita Gillmann <nikita@n0.is>
To: 41286@debbugs.gnu.org
Subject: [bug#41286] check for argp header
Date: Fri, 15 May 2020 14:30:27 +0200 [thread overview]
Message-ID: <20200515123016.gmeicqvo67qrqpuh@hex> (raw)
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
Hi,
as mentioned in IRC I have begun porting Guix to NetBSD (with the path
taken not yet decided upon, just plain building guix itself for now).
Glibc provides argp. Arguably we don't have to check for argp because
Guix targets glibc. But I am quiete certain that there will be people
who will attempt to do what I am doing and run into this.
I haven't tested this, but semantically it should check out. I don't
know how much changed in guix's bootstrap but configure.ac should still be
the right place for this patch.
[-- Attachment #2: 0001-configure-check-for-arpg-header-as-required-by-nix.patch --]
[-- Type: text/plain, Size: 758 bytes --]
From eb8214d2cd6b2170f6e05b89dbd8e47e1f0f4326 Mon Sep 17 00:00:00 2001
From: nikita <nikita@n0.is>
Date: Fri, 15 May 2020 14:23:48 +0200
Subject: [PATCH] configure: check for arpg header as required by nix.
This is provided by glibc, porting to a platform without glibc
revealed this lack of check.
---
configure.ac | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configure.ac b/configure.ac
index 0a20b476eb..174633785a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -266,6 +266,9 @@ else
fi
AC_SUBST([LIBLZ])
+# check for standard headers, required in Nix daemon
+AC_CHECK_HEADERS([argp.h])
+
dnl Check for Guile-SSH, for the (guix ssh) module.
GUIX_CHECK_GUILE_SSH
AM_CONDITIONAL([HAVE_GUILE_SSH],
--
2.25.2
next reply other threads:[~2020-05-15 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 12:30 Nikita Gillmann [this message]
2020-05-16 17:22 ` [bug#41286] check for argp header 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=20200515123016.gmeicqvo67qrqpuh@hex \
--to=nikita@n0.is \
--cc=41286@debbugs.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 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).