public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/106156] [13 Regression] libtool fails to link liblto_plugin.la on riscv64-linux-gnu
Date: Mon, 04 Jul 2022 10:24:24 +0000 [thread overview]
Message-ID: <bug-106156-4-ybnVTUF3cL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106156-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106156
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kito at gcc dot gnu.org,
| |wilson at gcc dot gnu.org
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
All right, so now I see:
[ 7129s] libtool: link:
/home/abuild/rpmbuild/BUILD/gcc-13.0.0+git194120/obj-riscv64-suse-linux/./prev-gcc/xgcc
-B/home/abuild/rpmbuild/BUILD/gcc-13.0.0+git194120/obj-riscv64-suse-linux/./prev-gcc/
-B/usr/riscv64-suse-linux/bin/ -B/usr/riscv64-suse-linux/bin/
-B/usr/riscv64-suse-linux/lib/ -isystem /usr/riscv64-suse-linux/include
-isystem /usr/riscv64-suse-linux/sys-include -fno-checking -shared -fPIC
-DPIC .libs/lto-plugin.o -pthread -static-libgcc
-Wl,--version-script=../../lto-plugin/lto-plugin.map -static-libstdc++
-static-libgcc ../libiberty/pic/libiberty.a -pthread -Wl,-soname
-Wl,liblto_plugin.so -o .libs/liblto_plugin.so
[ 7129s] /usr/riscv64-suse-linux/bin/ld: cannot find -latomic: No such file or
directory
[ 7129s] collect2: error: ld returned 1 exit status
[ 7129s] make[4]: *** [Makefile:472: liblto_plugin.la] Error 1
which is strange because libatomic package is installed in the build root.
Can please riscv64 folks chime in?
next prev parent reply other threads:[~2022-07-04 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 4:26 [Bug bootstrap/106156] New: " doko at gcc dot gnu.org
2022-07-01 7:06 ` [Bug bootstrap/106156] " rguenth at gcc dot gnu.org
2022-07-01 7:28 ` marxin at gcc dot gnu.org
2022-07-04 10:24 ` marxin at gcc dot gnu.org [this message]
2022-07-04 10:31 ` pinskia at gcc dot gnu.org
2022-07-04 11:03 ` marxin at gcc dot gnu.org
2022-07-04 11:32 ` marxin at gcc dot gnu.org
2022-07-08 11:21 ` marxin at gcc dot gnu.org
2022-07-13 7:35 ` doko at gcc dot gnu.org
2022-07-13 7:40 ` marxin at gcc dot gnu.org
2022-07-14 11:27 ` cvs-commit at gcc dot gnu.org
2022-07-14 11:28 ` marxin 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-106156-4-ybnVTUF3cL@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).