From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Ian Lance Taylor via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: gofrontend-dev <gofrontend-dev@googlegroups.com>,
Ian Lance Taylor <iant@golang.org>
Subject: Re: libgo patch committed: Update to Go1.18rc1 release
Date: Sun, 20 Feb 2022 23:13:23 +0100 [thread overview]
Message-ID: <ydd4k4t1918.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAOyqgcVcV6cHc4GHt0aPShU=-xGePS6+cvkY5EoBBLtKTh1j3g@mail.gmail.com> (Ian Lance Taylor via Gcc-patches's message of "Fri, 18 Feb 2022 13:14:38 -0800")
Hi Ian,
> This patch updates libgo to the Go1.18rc1 release. Bootstrapped and
> ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
this broke Solaris bootstrap:
ld: fatal: file runtime/internal/.libs/syscall.o: open failed: No such file or directory
collect2: error: ld returned 1 exit status
Creating a dummy syscall_solaris.go worked around that for now.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-02-20 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 21:14 Ian Lance Taylor
2022-02-20 22:13 ` Rainer Orth [this message]
2022-02-21 21:24 ` Ian Lance Taylor
2022-02-22 12:09 ` Rainer Orth
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=ydd4k4t1918.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).