public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/106156] New: [13 Regression] libtool fails to link liblto_plugin.la on riscv64-linux-gnu
Date: Fri, 01 Jul 2022 04:26:23 +0000 [thread overview]
Message-ID: <bug-106156-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106156
Bug ID: 106156
Summary: [13 Regression] libtool fails to link liblto_plugin.la
on riscv64-linux-gnu
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
seen with trunk 20220630 on riscv64-linux-gnu, using binutils trunk/2.39. Not
seen in the same environment building GCC 11 and 12:
/bin/bash ./libtool --tag=CC --tag=disable-static --mode=link
/<<PKGBUILDDIR>>/build/./prev-gcc
/xgcc -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/lib/gcc-snapshot/riscv64-linux-gnu/bin/ -B/usr
/lib/gcc-snapshot/riscv64-linux-gnu/bin/
-B/usr/lib/gcc-snapshot/riscv64-linux-gnu/lib/ -isystem
/usr/lib/gcc-snapshot/riscv64-linux-gnu/include -isystem
/usr/lib/gcc-snapshot/riscv64-linux-gn
u/sys-include -fno-checking -Wall -g -O2 -fno-checking -gtoggle -module
-avoid-version -bin
dir /usr/lib/gcc-snapshot/libexec/gcc/riscv64-linux-gnu/13
-export-symbols-regex onload -Xcom
piler '-static-libstdc++' -Xcompiler '-static-libgcc' '-Wl,-z,relro' -o
liblto_plugin.la -rpath
/usr/lib/gcc-snapshot/libexec/gcc/riscv64-linux-gnu/13 lto-plugin.lo
-Wc,../libiberty/pic/libib
erty.a
libtool: link: riscv64-linux-gnu-nm .libs/lto-plugin.o | | /bin/sed 's/.*
//' | sort | uniq
> .libs/liblto_plugin.exp
./libtool: eval: line 1118: syntax error near unexpected token `|'
./libtool: eval: line 1118: `riscv64-linux-gnu-nm .libs/lto-plugin.o | |
/bin/sed 's/.* //'
| sort | uniq > .libs/liblto_plugin.exp'
make[6]: *** [Makefile:471: liblto_plugin.la] Error 2
make[6]: Leaving directory '/<<PKGBUILDDIR>>/build/lto-plugin'
make[5]: *** [Makefile:382: all] Error 2
make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/lto-plugin'
make[4]: *** [Makefile:15935: all-stage2-lto-plugin] Error 2
GCC is configured with
Configured with: -v
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++
--prefix=/usr/lib/gcc-snapshot
--with-gcc-major-version-only
--program-prefix=
--enable-shared
--enable-linker-build-id
--disable-nls
--enable-clocale=gnu
--enable-libstdcxx-debug
--enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new
--enable-gnu-unique-object
--disable-libitm
--disable-libquadmath
--disable-libquadmath-support
--enable-plugin
--with-system-zlib
--enable-libphobos-checking=release
--with-target-system-zlib=auto
--enable-objc-gc=auto
--enable-multiarch
--disable-werror
--disable-multilib
--with-arch=rv64gc
--with-abi=lp64d
--enable-checking=yes
--build=riscv64-linux-gnu
--host=riscv64-linux-gnu
--target=riscv64-linux-gnu
next reply other threads:[~2022-07-01 4:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 4:26 doko at gcc dot gnu.org [this message]
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
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@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).