From: "Maciej W. Rozycki" <macro@wdc.com>
To: gcc-patches@gcc.gnu.org
Subject: [PING^2][PATCH v2 2/2] testsuite: Fix run-time tracking down of `libgcc_s'
Date: Tue, 17 Dec 2019 00:06:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.1912170003070.30965@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1911290526340.13542@redsun52.ssa.fujisawa.hgst.com>
On Fri, 29 Nov 2019, Maciej W. Rozycki wrote:
> Fix a catastrophic libgo testsuite failure in cross-compilation where
> the shared `libgcc_s' library cannot be found by the loader at run time
> in build-tree testing and consequently all test cases fail the execution
> stage, giving output (here with the `x86_64-linux-gnu' host and the
> `riscv64-linux-gnu' target, with RISC-V QEMU in the Linux user emulation
> mode as the target board) like:
>
> spawn qemu-riscv64 -E LD_LIBRARY_PATH=.:.../riscv64-linux-gnu/lib64/lp64d/libgo/.libs ./a.exe
> ./a.exe: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
> FAIL: archive/tar
Ping for:
<https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02610.html>
Maciej
prev parent reply other threads:[~2019-12-17 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 9:09 [PATCH v2 0/2] Fix run-time handling of `libgcc_s' in testing Maciej W. Rozycki
2019-11-29 9:09 ` [PATCH v2 1/2] driver: Do not warn about ineffective `-x' option if no inputs were given Maciej W. Rozycki
2019-11-29 21:00 ` Joseph Myers
2019-11-30 13:44 ` Maciej W. Rozycki
2019-11-29 9:16 ` [PATCH v2 2/2] testsuite: Fix run-time tracking down of `libgcc_s' Maciej W. Rozycki
2019-12-02 23:40 ` Ian Lance Taylor
2019-12-03 18:02 ` Maciej W. Rozycki
2019-12-09 21:30 ` [PING][PATCH " Maciej W. Rozycki
2019-12-21 1:39 ` Mike Stump
2019-12-22 0:32 ` Maciej W. Rozycki
2019-12-17 0:06 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.21.1912170003070.30965@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=gcc-patches@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).