On Wed, 12 Mar 2025 at 20:56, Dennis Clarke <dclarke@xxxxxxxxxxxxx> wrote: > > On 3/12/25 16:19, Jonathan Wakely wrote: > > On Wed, 12 Mar 2025 at 20:11, Dennis Clarke <dclarke@xxxxxxxxxxxxx> wrote: > >> > >> On 3/12/25 15:59, Jonathan Wakely wrote: > >>> On Wed, 12 Mar 2025 at 19:58, Dennis Clarke <dclarke@xxxxxxxxxxxxx> wrote: > >> t$ > >> t$ ./tz_test > >> ./tz_test: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version > >> `GLIBCXX_3.4.32' not found (required by ./tz_test) > >> ./tz_test: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version > >> `GLIBCXX_3.4.31' not found (required by ./tz_test) > >> t$ > >> > >> Now this is getting strange. > > > > No it isn't: > > https://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.how_to_set_paths > > > > You can just use -static-libstdc++ for this test. > > > > This sort of thing is none too helpful : > > > t$ > t$ LD_LIBRARY_PATH=/opt/bw/lib ./tz_test > ersatz > t$ > t$ LD_LIBRARY_PATH=/opt/bw/gcc14/lib64 ./tz_test > ersatz > t$ > > So I need to remove the default system GCC packages No, don't mess with the system GCC unless you know what you're doing (and the fact we're having this discussion about it says you don't really). > and then drop the > new /opt/bw/gcc14/lib64/libstdc++.so.6.0.33 thing into a well known > location for GCC to work right ? Really ? No, there are better solutions, as described at the link above, and the chapter of the libstdc++ manual that it links to.
