svn commit: r325954 - in head: . share/mk sys/conf usr.sbin/config

[Pedro Giffuni]

....
On 19/11/2017 17:38, Mark Millard wrote:
> Pedro Giffuni pfg at FreeBSD.org wrote on
> Sun Nov 19 15:29:33 UTC 2017 :
>
>> Yes, we should
>> avoid breaking existing stuff (however old) in ports but no one is
>> expecting to build modern FreeBSD with gcc 3.4 or even gcc 4.1. We did
>> what we could with gcc 4.2.1 but it's time is also over.
> Unfortunately for powerpc64 no alternative
> works fully. For example:
>
> A) With a buildworld by clang and C++ programs linked against
>     the system libraries, any C++ exception thrown causes the
>     program to crash: clang generates bad code in the library.
>
> B) Modern gcc's build a lib32 based on generating a messed up
>     crtbeginS.o content (bad register usage) and so 32-bit
>     programs crash.
>
> As far as I know gcc 4.2.1 is still the only environment that
> generally works for powerpc64.
Hmm ...
At some point some of the newer GCC was generating good code.
I have had reports of openoffice-devel working on FreeBSD powerpc64 and,
even on x86, openoffice stopped building with our base gcc.

> [There is no devel/powerpc-gcc like there is a devel/powerpc64-gcc
> and I've never managed to to make a working powerpc build from a
> gcc other than 4.2.1 . (A) prevents clang from counting as working
> overall. So powerpc may be in the same boat as powerpc64 as far as
> having a known way to build without gcc 4.2.1 goes.]
At least PPC64 is alive, I am afraid that I don't see a solution for 
sparc64.

But this is very off-topic to lint issue :).

Pedro.