all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, 61879@debbugs.gnu.org
Subject: Re: bug#61879: Powerpc on core-updates
Date: Thu, 13 Apr 2023 16:06:16 +0200	[thread overview]
Message-ID: <ZDgMWFJX8Sn/XLrf@jurong> (raw)
In-Reply-To: <87mt3byjrp.fsf@cbaines.net>

Am Thu, Apr 13, 2023 at 02:46:00PM +0100 schrieb Christopher Baines:
> Thanks for figuring this out Andreas! I've managed to apply this change
> in the relevant place, and it appears to work.

Good news, thanks!

> +          #$@(if (and (target-ppc64le?)
> +                      (version>=? (package-version gcc) "11"))

The file changed a lot on master, and the patch will not apply and
should not be needed there. I did not check, but I think it is already
not needed for gcc@12 any more. So we should probably check for the
major version being equal to 11.

It should be easy to check that it does not cause any rebuilds on the
other architectures, and we cannot break powerpc more than it already
is, so feel free to push something along these lines to core-updates.

Andreas



  reply	other threads:[~2023-04-13 14:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 23:16 bug#61879: [core-updates] libstdc++ fails to build on powerpc64le-linux Ludovic Courtès
2023-04-13  9:32 ` Powerpc on core-updates Andreas Enge
2023-04-13  9:51   ` Andreas Enge
2023-04-13 13:46   ` bug#61879: " Christopher Baines
2023-04-13 14:06     ` Andreas Enge [this message]
2023-04-13 16:57 ` bug#61879: Patch Andreas Enge
2023-04-14  8:15   ` Andreas Enge
2023-04-14  8:20     ` Christopher Baines
2023-04-14  9:42       ` Andreas Enge
2023-04-14 10:37         ` Christopher Baines
2023-04-14 12:10           ` Andreas Enge

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=ZDgMWFJX8Sn/XLrf@jurong \
    --to=andreas@enge.fr \
    --cc=61879@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.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.