On Sun, 8 Nov 2015, Pedro Giffuni wrote: > Great! We already worked around the issue by disabling > stack-protector-strong for gcc48 though.
Yep - it still felt like the right thing to also address this in the port. > What looks somewhat strange to me is that lang/gcc is an independent > port when it should just be a link to the current gcc default. This is the direction I'm working towards by establishing lang/gccX-devel ports (for snapshots) in addition to ang/gccX ports (for releases). > BTW, perhaps it’s time to bump the default gcc to gcc49? ;). Absolutely. Sadly there is a fair amount of broken software out there, and while we are close, having to fix/work around all of that has been delaying things. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196712 . In case you (or anyone else) want to help, I created a couple of bug reports that now are marked as blocking this upgrade. Help definitely appreciated. Gerald _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
