https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |UNCONFIRMED
Ever confirmed|1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
--- Comment #6 from Richard Biener ---
The libgcc_s.so link shouldn't reference anything from libstdc++ so this is
really odd.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
--- Comment #5 from Artem S. Tashkinov ---
Using the official tar.xz file of course, without any
changes/modifications/patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
--- Comment #4 from Artem S. Tashkinov ---
(In reply to Andrew Pinski from comment #3)
> How are you building gcc?
> What configure options are being passed?
> What make options are being passed?
> Do you have any env variables set that might ef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-05-22
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
--- Comment #2 from Artem S. Tashkinov ---
This workaround of mine is not really good: after `make install` you end up
with /opt/gcc/lib64/libstdc++.so.6.0.29 which is not GCC's but the system one
(/usr/lib64/libstdc++.so.6.0.30.so).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105688
--- Comment #1 from Artem S. Tashkinov ---
In /tmp/OBJDIR/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs I replaced the built
libstdc++.so.29 _three times_ with the system one (libstdc++.so.30) and it all
worked.
Still this looks like a serious bug
