On 2018-09-11 15:21, Martin Husemann wrote:
On Tue, Sep 11, 2018 at 09:17:34AM -0400, Mouse wrote:[...gcc...VAX...][...gcc...VAX...]This leads me to ask, why track gcc version changes? If switching to pcc is being seriously considered, why not just freeze at some specific version of gcc that's known to work?As long as I have VAX hardware there has never been any gcc version that I would say "is known to work".
There has definitely been, but I would not be able to pinpoint it now. But I used to do native builds on VAX in the past, and it would mostly work. At a few moments it actually managed to run through all of it, but for a long time there was issues with C++, which caused problems with groff.
And nowadays a lot of userland stuff is C++, so until pcc supports that I think gcc is an absolute must (unfortunately).
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt%softjar.se@localhost || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol