From: Andreas Enge <andreas@enge.fr>
To: 62949@debbugs.gnu.org
Cc: 62936@debbugs.gnu.org
Subject: bug#62949: libgcrypt version in core-updates
Date: Wed, 19 Apr 2023 18:28:31 +0200 [thread overview]
Message-ID: <ZEAWryOf8oblZG1l@jurong> (raw)
Hello,
this looks to me like it could be a duplicate of #62936, but since this
bug is closed, I am simply opening a new one.
The libgcrypt version was updated from 1.8.8 to 1.10.1 from master to
core-updates.
This causes ./configure to fail like so:
...
checking for gcry_md_open in -lgcrypt... no
checking for gcrypt.h... yes
configure: error: GNU libgcrypt not found; please install it
I suppose that the same problem occurred in #62936, but did not manifest
itself as clearly since one usually does not rerun configure.
It looks as if the API changed incompatibly between the two versions.
Andreas
next prev reply other threads:[~2023-04-19 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:51 bug#62936: [core-updates] pre-inst-env no longer works Brian Cully via Bug reports for GNU Guix
2023-04-19 8:51 ` Simon Tournier
2023-04-19 11:29 ` Brian Cully via Bug reports for GNU Guix
2023-04-19 13:41 ` Ludovic Courtès
2023-04-19 14:14 ` Brian Cully via Bug reports for GNU Guix
2023-04-19 16:28 ` Andreas Enge [this message]
2023-04-19 16:37 ` bug#62949: libgcrypt version in core-updates Ludovic Courtès
2023-04-19 18:19 ` Andreas Enge
2023-04-19 20:40 ` Ludovic Courtès
2023-04-19 19:51 ` bug#62936: [core-updates] pre-inst-env no longer works Brian Cully via Bug reports for GNU Guix
2023-04-24 8:34 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-24 14:44 ` Brian Cully via Bug reports for GNU Guix
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=ZEAWryOf8oblZG1l@jurong \
--to=andreas@enge.fr \
--cc=62936@debbugs.gnu.org \
--cc=62949@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).