From: Vagrant Cascadian <vagrant@debian.org>
To: 46334@debbugs.gnu.org
Subject: bug#46334: mbedtls-apache fails to build on aarch64
Date: Fri, 05 Feb 2021 13:19:39 -0800 [thread overview]
Message-ID: <87a6sib4b8.fsf@yucca> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
I get the following error when building mbedtls-apache on aarch64:
/tmp/guix-build-mbedtls-apache-2.23.0.drv-0/source/programs/ssl/ssl_context_info.c:
In function ‘read_next_b64_code’:
/tmp/guix-build-mbedtls-apache-2.23.0.drv-0/source/programs/ssl/ssl_context_info.c:384:16:
error: comparison is always\
true due to limited range of data type [-Werror=type-limits]
while( EOF != c )
^~
cc1: all warnings being treated as errors
make[2]: ***
[programs/ssl/CMakeFiles/ssl_context_info.dir/build.make:66:
programs/ssl/CMakeFiles/ssl_context_info.dir\
/ssl_context_info.c.o] Error 1
make[2]: Leaving directory
'/tmp/guix-build-mbedtls-apache-2.23.0.drv-0/build'
make[1]: *** [CMakeFiles/Makefile2:2252:
programs/ssl/CMakeFiles/ssl_context_info.dir/all] Error 2
make[1]: Leaving directory
'/tmp/guix-build-mbedtls-apache-2.23.0.drv-0/build'
make: *** [Makefile:144: all] Error 2
command "make" "-j" "1" failed with status 2
The version which produced this particular error was guix commit
7382b1027a319e505be6cfcadf1f5bd761dadccc, though the issue has been
present for quite some time.
Full build log attached.
live well,
vagrant
[-- Attachment #1.2: 5mdydmqz9c88gihgzm7m5f906w0fk6-mbedtls-apache-2.23.0.drv.bz2 --]
[-- Type: application/octet-stream, Size: 17130 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2021-02-05 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 21:19 Vagrant Cascadian [this message]
2021-02-05 21:32 ` bug#46334: mbedtls-apache fails to build on aarch64 Leo Famulari
2023-07-20 19:43 ` Vagrant Cascadian
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=87a6sib4b8.fsf@yucca \
--to=vagrant@debian.org \
--cc=46334@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).