From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 62936@debbugs.gnu.org, 62949@debbugs.gnu.org
Subject: bug#62949: libgcrypt version in core-updates
Date: Wed, 19 Apr 2023 18:37:08 +0200 [thread overview]
Message-ID: <877cu7hlqj.fsf@gnu.org> (raw)
In-Reply-To: <ZEAWryOf8oblZG1l@jurong> (Andreas Enge's message of "Wed, 19 Apr 2023 18:28:31 +0200")
Hallo!
Andreas Enge <andreas@enge.fr> skribis:
> 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.
Given that the ‘guix’ package builds fine on ‘core-updates’, it’s most
likely a build environment issue.
What does ‘config.log’ say?
Ludo’.
next prev parent reply other threads:[~2023-04-19 16:38 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 ` bug#62949: libgcrypt version in core-updates Andreas Enge
2023-04-19 16:37 ` Ludovic Courtès [this message]
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=877cu7hlqj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=62936@debbugs.gnu.org \
--cc=62949@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).