From: Efraim Flashner <efraim@flashner.co.il>
To: Marcel van der Boom <marcel@van-der-boom.nl>
Cc: 56680@debbugs.gnu.org
Subject: bug#56680: go-1.16.15 build fails in check phase on powerpc64le
Date: Fri, 5 Aug 2022 00:34:30 +0300 [thread overview]
Message-ID: <Yuw7ZpaiR2Y8wk+Y@pbp> (raw)
In-Reply-To: <87a68jen3l.fsf@van-der-boom.nl>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Thu, Aug 04, 2022 at 11:02:53PM +0200, Marcel van der Boom wrote:
>
> [Efraim Flashner]:
> > I'm currently working on bootstrapping go-1.17.11 directly from gccgo,
> > so we'd be able to skip 1.16 entirely. Currently it works on
> > x86_64-linux but not on riscv64-linux. If you want to test something
> > like that on powerpc64le that'd be great.
>
> Sure, can you point me in the right direction and get me started on what
> would be useful for you?
Looking at the package definitions for go it looks like the inputs and
native-inputs need to be cleaned up some, but for our purposes I think
just removing the native-inputs field completely from 1.17 should try to
make go-1.17 build with gccgo. Then try to build go@1.17.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-04 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:05 bug#56680: go-1.16.15 build fails in check phase on powerpc64le Marcel van der Boom
2022-08-04 16:24 ` Marcel van der Boom
2022-08-04 17:48 ` Efraim Flashner
2022-08-04 21:02 ` Marcel van der Boom
2022-08-04 21:34 ` Efraim Flashner [this message]
2022-08-09 13:19 ` Marcel van der Boom
2023-02-14 15:30 ` Marcel van der Boom
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=Yuw7ZpaiR2Y8wk+Y@pbp \
--to=efraim@flashner.co.il \
--cc=56680@debbugs.gnu.org \
--cc=marcel@van-der-boom.nl \
/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.