all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 68321@debbugs.gnu.org, Munyoki Kilyungi <me@bonfacemunyoki.com>,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	Efraim Flashner <efraim@flashner.co.il>,
	Benjamin Slade <slade@lambda-y.net>, jgart <jgart@dismail.de>
Subject: [bug#68321] Request for merging "lisp-team" branch
Date: Tue, 09 Jan 2024 14:10:17 +0000	[thread overview]
Message-ID: <87v882h9dl.fsf@kitej> (raw)
In-Reply-To: <aT6jGU2T760eM3oQhXauRXzdoBHbYF_GlG7lW84M2wSveNkCjnsktMc4auIc7QNQNodDF-vp8UeHTTRFUaqqWf4i8TGsW-s7VNJ1cqysWKU=@apatience.com>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

"Paul A. Patience" <paul@apatience.com> skribis:

> On Monday, January 8th, 2024 at 1:12 PM, Efraim Flashner <efraim@flashner.co.il> wrote:
>> I have sbcl@2.4.0 from the lisp-team branch failing to build on
>> powerpc64le and succeeding on aarch64-linux.
>>
>> riscv64-linux failed for me too:
>
> I don't have a ppc64le machine, and I don't know about riscv64,
> but SBCL 2.4.0 needs a patch to build on ppc64 [1].
>
> [1]: https://github.com/sbcl/sbcl/commit/255f3ead060129aa097b62f10d054cdc4997a431

I adapted the patch from upstream and added it to the lisp-team branch.

I tried testing the build with "guix build -s powerpc46le-linux sbcl"
on my x86-64 machine, but it failed indicating that the clisp used to
boostrap sbcl isn't working properly. I don't know if the problem comes
from qemu or if clisp is really broken on powerpc64le.
Efraim, could you check on your powerpc64le machine?

I also tried "guix build -s riscv64-linux sbcl", but it didn't work,
because some dependencies fail to build (like gnutls).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2024-01-09 14:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 13:06 [bug#68321] Request for merging "lisp-team" branch Guillaume Le Vaillant
2024-01-08 18:12 ` Efraim Flashner
2024-01-09  0:35   ` Paul A. Patience
2024-01-09 14:10     ` Guillaume Le Vaillant [this message]
2024-01-09 16:59       ` Efraim Flashner
2024-01-09 17:36       ` Efraim Flashner
2024-01-09 20:24       ` Efraim Flashner
2024-01-10 10:45         ` Guillaume Le Vaillant
2024-01-10 11:01           ` Efraim Flashner
2024-01-10 13:08             ` Guillaume Le Vaillant
2024-01-10 22:10               ` Guillaume Le Vaillant
2024-01-11 13:50 ` 郑俊杰
2024-01-11 13:57   ` Guillaume Le Vaillant
2024-01-11 17:07     ` bug#68321: " Guillaume Le Vaillant

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=87v882h9dl.fsf@kitej \
    --to=glv@posteo.net \
    --cc=68321@debbugs.gnu.org \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=efraim@flashner.co.il \
    --cc=jgart@dismail.de \
    --cc=me@bonfacemunyoki.com \
    --cc=paul@apatience.com \
    --cc=slade@lambda-y.net \
    /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.