Date: Wed, 16 Aug 2017 03:48:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 221288] lang/gcc5 links against libsupc++ when compiling Message-ID: <bug-221288-29464-qyJmsSz8pP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221288-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-221288-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221288 --- Comment #11 from Mark Millard <markmi@dsl-only.net> --- Trying my standard-C++ program that uses C++ threads in a more modern context (head -r322287, lang/gcc7) in an amd64 context under a Virtual Box virtual machine (that is running on Windows 10 Pro). . . # g++7 -std=3Dc++14 -Wpedantic -Wall -pthread -Wl,-rpath=3D/usr/local/lib/g= cc7 -O2 cpp_clocks_investigation.cpp # ldd a.out a.out: libstdc++.so.6 =3D> /usr/local/lib/gcc7/libstdc++.so.6 (0x800844000) libm.so.5 =3D> /lib/libm.so.5 (0x800bd8000) libgcc_s.so.1 =3D> /usr/local/lib/gcc7/libgcc_s.so.1 (0x800e05000) libthr.so.3 =3D> /lib/libthr.so.3 (0x80101c000) libc.so.7 =3D> /lib/libc.so.7 (0x801244000) # ./a.out . . . (omitted) . . . Segmentation fault (core dumped) # g++7 -std=3Dc++14 -Wpedantic -Wall -pthread -O2 cpp_clocks_investigation.= cpp# ldd a.out a.out: libstdc++.so.6 =3D> /usr/local/lib/gcc7/libstdc++.so.6 (0x800844000) libm.so.5 =3D> /lib/libm.so.5 (0x800bd8000) libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x800e05000) libthr.so.3 =3D> /lib/libthr.so.3 (0x80101b000) libc.so.7 =3D> /lib/libc.so.7 (0x801243000) # ./a.out . . . (omitted) . . . End of clock tests. So it worked for /lib/libgcc_s.so.1 but not for /usr/local/lib/gcc7/libgcc_s.so.1 and I must have been wrong about /lib/libcxxrt.so.1 being what mattered. This threading example is a context where -Wl,-rpath=3D/usr/local/lib/gcc7 prevents correct operation because of cross library dependencies on implementation details of the build-time context vs. the mismatched runtime context for libthr.so.3 vs. libgcc_s.so.1 . # clang++ -std=3Dc++14 -Wpedantic -Wall -pthread -O2 cpp_clocks_investigati= on.cpp # ldd a.out a.out: libc++.so.1 =3D> /usr/lib/libc++.so.1 (0x800844000) libcxxrt.so.1 =3D> /lib/libcxxrt.so.1 (0x800b10000) libm.so.5 =3D> /lib/libm.so.5 (0x800d2e000) libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x800f5b000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801171000) libc.so.7 =3D> /lib/libc.so.7 (0x801399000) # ./a.out . . . (omitted) . . . End of clock tests. So this also worked. Again /lib/libthr.so.3 and /lib/libgcc_s.so.1 go together just fine. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221288-29464-qyJmsSz8pP>