Fwd: [Bug 239813] Update lang/gcc9, lang/gcc9-devel, lang/gcc8, and lang/gcc8-devel to ELFv2 ABI on powerpc64

[John Baldwin]

On 11/19/19 10:34 AM, Mark Millard wrote:
> [A similar question to the below exists for base/gcc . The lang/gcc* are being ELFv2 enabled for powerpc64 by checking the environment for if it is new enough and already is ELFv2 based.]
> 
> Begin forwarded message:
> 
> From: bugzilla-noreply at freebsd.org
> Subject: [Bug 239813] Update lang/gcc9, lang/gcc9-devel, lang/gcc8, and lang/gcc8-devel to ELFv2 ABI on powerpc64
> Date: November 19, 2019 at 09:32:52 PST
> To: marklmi26-fbsd at yahoo.com
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239813
> 
> Gerald Pfeifer <gerald at FreeBSD.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>            Summary|Update lang/gcc8 and        |Update lang/gcc9,
>                   |lang/gcc9 to ELFv2 ABI on   |lang/gcc9-devel, lang/gcc8,
>                   |powerpc64                   |and lang/gcc8-devel to
>                   |                            |ELFv2 ABI on powerpc64
> 
> --- Comment #38 from Gerald Pfeifer <gerald at FreeBSD.org> ---
> (In reply to Mark Millard from comment #35)
>> I do not know the intent for devel/powerpc64-gcc relative
>> to future ELFv2 ABI use. Does it need anything? (May be
>> it is updating to gcc9 or some such first?)
> 
> Updating to GCC 9 would be my recomendation, though I have no
> involvement with that port.
> 
> lang/gcc9-devel should be fine now, both wrt. the new ABI as well
> as building with clang.
> 
> Next I'll make the remaining equivalent changes to lang/gcc9 and
> lang/gcc8-devel.

I've just committed a new devel/freebsd-gcc6 port (with flavors) to replace
the powerp64-gcc port (and slaves) with an intention of creating a
freebsd-gcc9 port as a followup.  It seems once freebsd-gcc9 exists we can
apply this change to that.

base/gcc will also similarly be adjusted to base/gcc6 and base/gcc9 in the
future.

The reason to keep old versions is that gcc6 is known to work (for some value
of work) for existing releases, so we want to provide different packages for
different major compiler versions to cope with newer OS releases supporting
newer compilers (e.g. we will patch head to work with freebsd-gcc9, but if
we only had a single powerpc64-gcc port we wouldn't be able to provide a
working compiler for stable/11 if we changed powerpc64-gcc to GCC 9).

-- 
John Baldwin