From: Leo Famulari <leo@famulari.name>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 45826@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
guix-sysadmin@gnu.org
Subject: bug#45826: SBCL / Common Lisp packages fail to build on aarch64
Date: Sat, 16 Jan 2021 13:58:39 -0500 [thread overview]
Message-ID: <YAM3X0TOTT3VfakZ@jasmine.lan> (raw)
In-Reply-To: <877dod1al9.fsf@yamatai>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
On Sat, Jan 16, 2021 at 10:42:58AM +0100, Guillaume Le Vaillant wrote:
> When taking a look at the logs of failing builds of sbcl-* packages on
> aarch64-linux (for example at [1] for master or at [2] for staging),
> I saw that the build jobs try to build sbcl (which is currently failing)
> for every package.
>
> I would have expected the builds for sbcl-* packages to be marked as
> "failed because missing dependency" given that the main dependency of
> the asdf-build-system/sbcl failed to build. Instead the build farm is
> trying to rebuild sbcl over and over, which wastes quite some time and
> resources.
>
> It looks like the dependencies of the build system are not considered as
> dependencies for the packages that use this build system.
> Am I missing something?
That's a good observation. I hadn't thought of it.
I'm CC-ing Mathieu Othacehe and guix-sysadmin so that we can disable
these builds until we can fix the bug for real. Mathieu: this might
explain why the build farm is spending all its effort on aarch64.
By the way, SBCL can be built for aarch64 according to Efraim:
http://logs.guix.gnu.org/guix/2021-01-13.log#105652
So, the original point of this bug is obviated, and I'm re-titling it to
address your observation, Guillaume.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-16 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 21:04 bug#45826: SBCL / Common Lisp packages fail to build on aarch64 Leo Famulari
2021-01-13 21:03 ` Guillaume Le Vaillant
2021-01-13 23:25 ` Leo Famulari
2021-01-16 9:42 ` Guillaume Le Vaillant
2021-01-16 18:58 ` Leo Famulari [this message]
2021-01-17 9:29 ` Mathieu Othacehe
2021-01-17 11:35 ` Christopher Baines
2021-01-18 13:36 ` Mathieu Othacehe
2021-01-17 19:11 ` Leo Famulari
2021-01-17 19:37 ` Efraim Flashner
2021-01-19 13:13 ` Ludovic Courtès
2021-01-19 20:17 ` Leo Famulari
2021-02-01 20:56 ` Ludovic Courtès
2021-02-01 21:13 ` Leo Famulari
2021-02-01 22:03 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YAM3X0TOTT3VfakZ@jasmine.lan \
--to=leo@famulari.name \
--cc=45826@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=guix-sysadmin@gnu.org \
--cc=othacehe@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.