From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 33023-done@debbugs.gnu.org
Subject: bug#33023: configure: GUIX_ASSERT_LIBGCRYPT_USABLE: command not found
Date: Fri, 12 Oct 2018 15:19:35 +0200 [thread overview]
Message-ID: <878t33i9p4.fsf@gnu.org> (raw)
In-Reply-To: <87sh1biasz.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 12 Oct 2018 14:55:40 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Hi Mark,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Mark H Weaver <mhw@netris.org> writes:
>>
>>> When building the 'guix' package, or while running ./configure in a git
>>> checkout in an environment created by "guix environment guix", the
>>> following error occurs:
>>>
>>> ./configure: line 8083: GUIX_ASSERT_LIBGCRYPT_USABLE: command not found
>>
>> This bug was introduced by commit
>> ca719424455465fca4b872c371daf2a46de88b33 (Switch to Guile-Gcrypt), which
>> removed the GUIX_ASSERT_LIBGCRYPT_USABLE macro definition from
>> m4/guix.m4, although it's still used in configure.ac.
>
> Oops, indeed. I’ll just remove the use of GUIX_ASSERT_LIBGCRYPT_USABLE
> in configure.ac, which, as we’ve seen, is no longer needed. :-)
Done in 28f436a904cbfc2d7bb6e5e8d91de23c03b134b0.
Ludo'.
prev parent reply other threads:[~2018-10-12 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 6:21 bug#33023: configure: GUIX_ASSERT_LIBGCRYPT_USABLE: command not found Mark H Weaver
2018-10-12 6:54 ` Mark H Weaver
2018-10-12 12:55 ` Ludovic Courtès
2018-10-12 13:19 ` Ludovic Courtès [this message]
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=878t33i9p4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33023-done@debbugs.gnu.org \
--cc=mhw@netris.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).