Date: Sat, 02 Jul 2022 14:20:45 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 264979] archivers/c-blosc2: compiler crash on armv7 Message-ID: <bug-264979-29464-YPSoA3ZTk0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264979-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-264979-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=3D264979 --- Comment #11 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Robert Clausecker from comment #10) Bad combination ( wrong libgcc_s.so.1 ): # g++11 trivial.cpp # ldd a.out a.out: libstdc++.so.6 =3D> /usr/local/lib/gcc11/libstdc++.so.6 (0x42600000) libm.so.5 =3D> /lib/libm.so.5 (0x40c8a000) libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x419b2000) libc.so.7 =3D> /lib/libc.so.7 (0x430fe000) Various type of programs can have crash problems from such a mix. Good combination: # g++11 -Wl,-rpath=3D/usr/local/lib/gcc11 trivial.cpp # ldd a.out a.out: libstdc++.so.6 =3D> /usr/local/lib/gcc11/libstdc++.so.6 (0x42400000) libm.so.5 =3D> /lib/libm.so.5 (0x409a9000) libgcc_s.so.1 =3D> /usr/local/lib/gcc11/libgcc_s.so.1 (0x41072000) libc.so.7 =3D> /lib/libc.so.7 (0x43f5a000) (The examples are from an old bugzilla report's comments.) I was just curious about what was involved in your failing context (the port's gcc based build). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264979-29464-YPSoA3ZTk0>