[Bug 215193] lib/libc++: convert to a private library
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215193 Bug ID: 215193 Summary: lib/libc++: convert to a private library Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: feature Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-toolchain@FreeBSD.org Reporter: jbe...@freebsd.org Depends on: 215192 libc++ version is currently tied to a specific FreeBSD release. If third-party software depends on bleeding edge C++ features it may fail to build. And pulling newer version from ports is risky due to ABI mismatch. To avoid Perl-style blunder let's promote the port version instead. For example, FreeBSD 10.x cannot benefit from complete C++14 support. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215192 [Bug 215192] devel/libc++: phase out usage as part of USES=compiler:gcc-c++11-lib -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 215193] libc++ and libcxxrt: convert to a private library
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215193 Jan Beich (mail not working) changed: What|Removed |Added Summary|lib/libc++: convert to a|libc++ and libcxxrt: |private library |convert to a private ||library -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 215193] libc++ and libcxxrt: convert to a private library
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215193 --- Comment #1 from Jan Beich (mail not working) --- Another issue is on libc++-enabled systems libstdc++ from ports cannot be used. theraven@ proposed to link libstdc++ against libcxxrt (like in gcc42 case) but that often requires bleeding edge version of it. 11.0+ release model should accelerate updates adoption but relying on libsupc++ compatibility still leaves some gaps as FreeBSD tries to maintain ABI instead of leaving it to upstream. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 215193] libc++ and libcxxrt: convert to a private library
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215193 David Chisnall changed: What|Removed |Added CC||thera...@freebsd.org --- Comment #2 from David Chisnall --- I think that a better solution to this would be more frequent upstream imports into base (which should become a lot easier to push to users once we have packaged base). Making libc++ a private library would mean that it would not be possible for users to compile C++ programs without installing a port, which would be a major regression. If we did that, then there's little point having a C++ compiler in the base system at all. Libc++ aims to be backwards binary compatible, and so there shouldn't be any POLA violations from installing a newer one. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
[Bug 215125] clang: Turning on sanitizer options causes the test for non-existent function mallinfo() to pass
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215125 Dimitry Andric changed: What|Removed |Added CC||d...@freebsd.org Assignee|freebsd-toolchain@FreeBSD.o |d...@freebsd.org |rg | Status|New |In Progress --- Comment #1 from Dimitry Andric --- Interesting, this is because the sanitizers have several interceptors for Linux-specific functions and variables, and these cause the link to succeed. I will check with upstream how we can best solve this. Most likely these interceptors should be disabled completely for FreeBSD. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
