public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/95061] shared libgo library not found when running the testsuite
Date: Wed, 13 May 2020 18:47:20 +0000 [thread overview]
Message-ID: <bug-95061-4-8RqnwVf9HQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95061-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95061
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Ian Lance Taylor <ian@gcc.gnu.org>:
https://gcc.gnu.org/g:0d5d880994660e231f82b7cb1dcfab744158f7e0
commit r11-364-g0d5d880994660e231f82b7cb1dcfab744158f7e0
Author: Ian Lance Taylor <iant@golang.org>
Date: Wed May 13 11:12:01 2020 -0700
libgo: build syscall test with -static
This avoids problems finding libgo.so when running the test as root,
which invokes the test as a child process in various limited environments.
Fixes PR go/95061
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/233897
next prev parent reply other threads:[~2020-05-13 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 15:23 [Bug go/95061] New: " doko at debian dot org
2020-05-12 0:27 ` [Bug go/95061] " cvs-commit at gcc dot gnu.org
2020-05-12 0:32 ` cvs-commit at gcc dot gnu.org
2020-05-13 17:20 ` cvs-commit at gcc dot gnu.org
2020-05-13 18:47 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-13 18:52 ` ian at airs dot com
2020-05-14 20:37 ` cvs-commit at gcc dot gnu.org
2020-05-15 22:33 ` cvs-commit at gcc dot gnu.org
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=bug-95061-4-8RqnwVf9HQ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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.
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).