[Bug libstdc++/99172] Build failure with slibtool and vtv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172 gcc-user at riseup dot net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #14 from gcc-user at riseup dot net --- Thanks, I applied that commit as a patch against 10.2.0 and it fixes the issue on my end too!
[Bug libstdc++/99172] Build failure with slibtool and vtv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172 --- Comment #8 from gcc-user at riseup dot net --- > Is there something here that you want/need me to take care of? If you can make it so that -lvtv is never passed to libtool so that slibtool will also work with --enable-vtable-verify as described in this issue it would be very much appreciated.
[Bug libstdc++/99172] Build failure with slibtool and vtv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172 --- Comment #5 from gcc-user at riseup dot net --- Starting with gcc-10 gentoo is not going to enable --enable-vtable-verify by default anymore. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=63c16d8b5e71b5f8e6185965062cf9c836800c29
[Bug libstdc++/99172] Build failure with slibtool and vtv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172 --- Comment #4 from gcc-user at riseup dot net --- Thanks for the clarification, regardless -lvtv is then passed to the libtool implementation. With GNU libtool it is silently removed hiding the bug, while slibtool actually passes it to ld which fails when its not valid. Ideally -lvtv should never reach the libtool implementation in this case since its not valid. (It is unfortunate that GNU libtool has hidden issues like this among others for so long...) > I don't know why you want to use --enable-vtable-verify but it's not really > maintained as far as I can see. I was not aware of that, it is default in gentoo. Maybe they should change that? I will add that to the gentoo issue.
[Bug libstdc++/99172] Build failure with slibtool and vtv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172 --- Comment #2 from gcc-user at riseup dot net --- > Note swapping out parts of the build system isn't tested/supported. This is both a gcc and GNU libtool bug, gcc is passing invalid flags and libtool is silently hiding the fact. I understand that slibtool may be untested in gcc, but since its actually doing the right thing here and has several benefits over GNU libtool (Maintained and readable codebase) it would be very appreciated if this can be fixed. > Can you quote where the "invalid" -lvtv is present? Honestly the gcc build system is confusing for me, but see this comment from the gentoo issue. https://bugs.gentoo.org/767706#c7 Briefly it explained that -lvtv comes from -fvtable-verify=std in a gcc spec file and is propogated to Makefile.in by gcc/Makefile.def.
[Bug libstdc++/99172] New: Build failure with slibtool and vtv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172 Bug ID: 99172 Summary: Build failure with slibtool and vtv Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: gcc-user at riseup dot net Target Milestone: --- Created attachment 50227 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50227=edit Full build log. When building gcc with slibtool (https://dev.midipix.org/cross/slibtool) the build will fail in the libstdc++.la make target in libstdc++-v3/src. /usr/x86_64-pc-linux-gnu/bin/ld: cannot find -lvtv This doesn't occur with GNU libtool because it silently filters out the invalid -lvtv while slibtool does not. I attached a full build log. Also see this gentoo issue. https://bugs.gentoo.org/767706 To build gcc with slibtool: export MAKE='make LIBTOOL=rdlibtool' Unfortunately gcc doesn't respect the value of the MAKEFLAGS environment variable.
