--- Comment #3 from lionelb dot nospam at gmail dot com 2007-06-21 22:43
---
(In reply to comment #2)
> (In reply to comment #1)
>
> BTW what are the implications for exceptions of linking with -static-libgcc?
Ok, that was a RTFM, got it now.
--
http://gcc.gnu.org
--- Comment #1 from lionelb dot nospam at gmail dot com 2007-06-20 15:31
---
(In reply to comment #0)
I can work around this by symlinking:
to ../lib64/libgcc_s.so from
/var/scratch/lionelb/usr/gcc-4.1.2/lib/gcc/x86_64-unknown-linux-gnu/4.1.2
and:
to ../../lib/libgcc_s.so from
/var
--- Comment #2 from lionelb dot nospam at gmail dot com 2007-06-20 15:01
---
(In reply to comment #1)
> And this is not a bug, you need to setup LD_LIBRARY_PATH correctly to point
> to where the latest version of libstdc++ reside which means where
> --enable-version-specifi
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: lionelb dot nospam at gmail dot com
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32425
ReportedBy: lionelb dot nospam at gmail dot com
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32415
