https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
--- Comment #6 from Eric ---
same problem with gcc/6.2.0
/exe/gcc/6.2.0/lib64/libstdc++.so
/exe/gcc/6.2.0/lib64/libitm.so
links to /lib64/libgcc_s.so.1
/exe/gcc/6.2.0/lib64/libasan.so
/exe/gcc/6.2.0/lib64/liblsan.so
/exe/gcc/6.2.0/lib64/libci
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
--- Comment #5 from Markus Trippelsdorf ---
This question should be asked on the gcc-h...@gcc.gnu.org list.
Bugzilla is the wrong place for it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
--- Comment #4 from Eric ---
anyway the link is not consistent
what can I do in order to remove any system gcc + libs
to provide ONLY the gcc we compiled to our cluster users ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
--- Comment #2 from Eric ---
so I have to switch on gcc version 5 or 6
with incompatible ABI change in the C++ library ?
nice ;-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
--- Comment #3 from Markus Trippelsdorf ---
(In reply to Eric from comment #2)
> so I have to switch on gcc version 5 or 6
> with incompatible ABI change in the C++ library ?
>
> nice ;-)
No need to switch the ABI, you can use the old one jus
