From: Vagrant Cascadian <vagrant@debian.org>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix fails to build on aarch64
Date: Thu, 16 Dec 2021 16:16:21 -0800 [thread overview]
Message-ID: <87pmpwuluy.fsf@ponder> (raw)
In-Reply-To: <87sfusuxtm.fsf@ponder>
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]
On 2021-12-16, Vagrant Cascadian wrote:
> Ever since commit:
>
> 224d437fb4147fe9eae277cbc8d39e1ef54bf5c9 gnu: guix: Update to 2a621f1.
>
> I've been unable to build "guix" on aarch64, several test suites
> failed... I'll try to dig up the failures
Here are the failed tests...
test-name: maybe-remove-expired-cache-entries, first cleanup
location: /tmp/guix-build-guix-1.3.0-14.2a621f1.drv-0/source/tests/cache.scm:58
source:
+ (test-equal
+ "maybe-remove-expired-cache-entries, first cleanup"
+ '("a" "b" "c")
+ (test-cache-cleanup cache))
expected-value: ("a" "b" "c")
actual-value: ()
result: FAIL
test-name: maybe-remove-expired-cache-entries, cleanup needed
location: /tmp/guix-build-guix-1.3.0-14.2a621f1.drv-0/source/tests/cache.scm:70
source:
+ (test-equal
+ "maybe-remove-expired-cache-entries, cleanup needed"
+ '("a" "b" "c")
+ (test-cache-cleanup
+ cache
+ (call-with-output-file
+ (string-append cache "/last-expiry-cleanup")
+ (lambda (port) (display 0 port)))))
expected-value: ("a" "b" "c")
actual-value: ()
result: FAIL
test-name: file-needed/recursive
location: /tmp/guix-build-guix-1.3.0-14.2a621f1.drv-0/source/tests/gremlin.scm:70
source:
+ (test-assert
+ "file-needed/recursive"
+ (let* ((needed
+ (file-needed/recursive %guile-executable))
+ (pipe (dynamic-wind
+ (lambda ()
+ (setenv "LD_TRACE_LOADED_OBJECTS" "yup"))
+ (lambda ()
+ (open-pipe* OPEN_READ %guile-executable))
+ (lambda () (unsetenv "LD_TRACE_LOADED_OBJECTS")))))
+ (define ldd-rx
+ (make-regexp
+ "^[[:blank:]]+([[:graph:]]+ => )?([[:graph:]]+) .*$"))
+ (define (read-ldd-output port)
+ (let loop ((result '()))
+ (match (read-line port)
+ ((? eof-object?) (reverse result))
+ ((= (cut regexp-exec ldd-rx <>) m)
+ (if m
+ (loop (cons (match:substring m 2) result))
+ (loop result))))))
+ (define ground-truth
+ (remove
+ (cut string-prefix? "linux-vdso.so" <>)
+ (read-ldd-output pipe)))
+ (and (zero? (close-pipe pipe))
+ (lset= string=?
+ (pk 'truth ground-truth)
+ (pk 'needed needed)))))
actual-value: #f
result: FAIL
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-12-17 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 19:57 guix fails to build on aarch64 Vagrant Cascadian
2021-12-17 0:16 ` Vagrant Cascadian [this message]
2021-12-17 8:59 ` Ricardo Wurmus
-- strict thread matches above, loose matches on Subject: below --
2022-01-02 20:31 Akira Kyle
2022-01-04 1:27 Akira Kyle
2022-01-04 14:30 ` Pierre Langlois
2022-01-09 4:45 ` Chris Marusich
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=87pmpwuluy.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@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).