all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sus Amogus <iskrim666@gmail.com>
To: 66205@debbugs.gnu.org
Subject: bug#66205: GuixSD on powerpc64le
Date: Tue, 26 Sep 2023 00:12:29 +0200	[thread overview]
Message-ID: <CAHooFsupF16_HNSqdA8xqc=awSegSCDh1ev=9YwEYKHy-60AWg@mail.gmail.com> (raw)

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

I'm currently working on building Guix System for powerpc64le, and I've
encountered a few issues that I could use some assistance with.

Firstly, linux-initrd failing because gcc-7.5 package used for
bootstrap-glibc do not support --with-long-double-128. Removing this works
just fine -- with last gcc package:
> /gnu/packages/make-bootstrap.scm
> (native-inputs
>     `(("gcc" ,gcc-7.5)
>         ,@(package-native-inputs base)))

I'm curious why gcc-7.5 was built without --with-long-double-128,
especially considering it's defined for powerpc64le-linux in
/gnu/packages/gcc.scm under (gcc-configure-flags-for-triplet).

Furthermore, I've encountered issues with Grub, which are detailed in this
issue: https://issues.guix.gnu.org/54407. I believe that porting
gcc-12-multilib from Debian could potentially resolve this problem.

Lastly, any image generated from (system-disk-image) depends on
grub-efi{,32}, but (a) grub-efi build fails on ppc*, and (b) ppc* systems
do not use EFI.

The remaining problems mostly involve software patching or minor code
adjustments.

Best regards,

Mykhailo Chernysh
iskrim666@gmail.com

[-- Attachment #2: Type: text/html, Size: 1747 bytes --]

             reply	other threads:[~2023-09-26 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 22:12 Sus Amogus [this message]
2023-09-28 18:38 ` bug#66205: GuixSD on powerpc64le jbranso--- via Bug reports for GNU Guix

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='CAHooFsupF16_HNSqdA8xqc=awSegSCDh1ev=9YwEYKHy-60AWg@mail.gmail.com' \
    --to=iskrim666@gmail.com \
    --cc=66205@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 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.