From: Sam James <sam@gentoo.org>
To: 65674@debbugs.gnu.org, bug-gnulib@gnu.org
Subject: bug#65674: Build failure with <openssl-3
Date: Fri, 01 Sep 2023 09:05:17 +0100 [thread overview]
Message-ID: <87edjie2qt.fsf@gentoo.org> (raw)
Hello,
Forwarding a downstream report at https://bugs.gentoo.org/913368
of coreutils-9.4 failing to build with openssl-1.1.x:
"""
x86_64-pc-linux-gnu-gcc -I. -I./lib -DHASH_ALGO_BLAKE2=1 -DHAVE_CONFIG_H -Ilib -I./lib -Isrc -I./src -O2 -march=x86-64 -pipe -pipe -frecord-gcc-switches -fno-diagnostics-color -fmessage-length=0 -c -o src/b2sum-digest.o `test -f 'src/digest.c' || echo './'`src/digest.c
In file included from src/digest.c:41:
./lib/md5.h:36:12: fatal error: openssl/configuration.h: No such file or directory
36 | # include <openssl/configuration.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
"""
This appears to have been introduced with gnulib commit
a436f5f498d7e747864d40d4450fa8330dd44d12.
configuration.h is only available with >=openssl-3.
thanks,
sam
next reply other threads:[~2023-09-01 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 8:05 Sam James [this message]
2023-09-01 13:00 ` bug#65674: Build failure with <openssl-3 Bruno Haible
2023-09-01 14:21 ` bug#65674: (no subject) Agostino Sarubbo
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://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edjie2qt.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=65674@debbugs.gnu.org \
--cc=bug-gnulib@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).