From: Caliph Nomble via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 45545@debbugs.gnu.org
Subject: bug#45545: gsasl fails to build on aarch64
Date: Wed, 30 Dec 2020 01:48:38 +0000 [thread overview]
Message-ID: <pspIlm25xz9h7NI_f9b3fvUPLTicAMlVQ9FWw3aWAVM9N0xEgr_yJSAfqgbr0dWg9ylPh4Pd1cMp5KjKsxJyhScoCRN_yIh6jc2vDLphhuM=@protonmail.com> (raw)
Hi,
The package gsasl fails to cross-compile to aarch64 on an x86_64 machine
(tested most recently on commit 8e128df5bf), at least, on mine. It seems to not
recognize libgcrypt during configure, even though it's listed in the package's
inputs. The build log is long, so I'll just list the important parts:
> ...
> phase `patch-source-shebangs' succeeded after 0.2 seconds
> starting phase `configure'
> configure flags: ("CC_FOR_BUILD=gcc" "CONFIG_SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "--prefix=/gnu/store/5isgg257zhlfczz20nf2rza2fibfaw7q-gsasl-1.8.1" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--host=aarch64-linux-gnu" "--with-gssapi-impl=mit" "--disable-static")
> ...
> checking for __builtin_expect... yes
> checking byteswap.h usability... yes
> checking byteswap.h presence... yes
> checking for byteswap.h... yes
> checking for libgcrypt-config... no
> checking for LIBGCRYPT - version >= 1.4.4... no
> configure: error: libgcrypt is too old
> configure: error: ./configure failed for lib
> command "/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "./configure" "CC_FOR_BUILD=gcc" "CONFIG_SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "--prefix=/gnu/store/5isgg257zhlfczz20nf2rza2fibfaw7q-gsasl-1.8.1" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--host=aarch64-linux-gnu" "--with-gssapi-impl=mit" "--disable-static" failed with status 1
The specific configure script failing seems to be lib/configure. Tell me if,
and how, I should include any more of the log.
This seems to be more of a problem since commit 72861d8ed4, since rottlog now
indirectly depends on gsasl, and rottlog is one of the base services. The
following command, thus, replicates the issue:
> guix system disk-image --image-type=pine64-raw -e '(@ (gnu system images pine64) pine64-barebones-os)'
Thanks!
next reply other threads:[~2020-12-30 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 1:48 Caliph Nomble via Bug reports for GNU Guix [this message]
2020-12-31 12:43 ` bug#45545: gsasl fails to build on aarch64 Efraim Flashner
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='pspIlm25xz9h7NI_f9b3fvUPLTicAMlVQ9FWw3aWAVM9N0xEgr_yJSAfqgbr0dWg9ylPh4Pd1cMp5KjKsxJyhScoCRN_yIh6jc2vDLphhuM=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=45545@debbugs.gnu.org \
--cc=calnomble@protonmail.com \
/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).