unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: 52436@debbugs.gnu.org
Subject: bug#52436: [patch] autoconf: Check for gperf if running from git
Date: Sat, 11 Dec 2021 15:58:06 +0100	[thread overview]
Message-ID: <87h7bfrxw9.fsf@web.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 49 bytes --]

Hi,

the attached patch adds a check for gperf.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-autoconf-Check-for-gperf-if-running-from-git.patch --]
[-- Type: text/x-patch, Size: 884 bytes --]

From 478eb18a38eb8d15cc96fde148842cf0329bfba5 Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide <arne_bab@web.de>
Date: Mon, 11 Oct 2021 07:33:23 +0200
Subject: [PATCH] autoconf: Check for gperf if running from git

this avoids breaking at runtime.
---
 configure.ac | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/configure.ac b/configure.ac
index bd49bf162..bd4e9fd2f 100644
--- a/configure.ac
+++ b/configure.ac
@@ -80,6 +80,15 @@ else
   fi
 fi
 
+# Check for gperf if running from git
+AC_MSG_CHECKING([Checking for gperf if built from git])
+if ! test -f ".tarball-version" && false; then
+  AC_CHECK_TOOL([GPERF], [gperf], [no])
+  if test x"$GPERF" = x"no"; then
+    AC_MSG_ERROR([Building from git requires gperf, but it could not be found. Please install gperf.])
+  fi
+fi
+
 gl_EARLY
 AC_PROG_CPP
 AC_PROG_SED
-- 
2.34.0


[-- Attachment #1.3: Type: text/plain, Size: 101 bytes --]


Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

                 reply	other threads:[~2021-12-11 14:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7bfrxw9.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=52436@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.
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).