Re: Same procedure as every year: GCC defaults change (GCC 9)

Aurelien Jarno <[email protected]>
Newsgroups gmane.linux.debian.ports.amd64
Message-ID <20190727221750.GB31317__12061.7379712471$1564265920$gmane$org@aurel32.net>
On 2019-07-27 17:28, Matthias Klose wrote:
> GCC 9 was released earlier this year, it is now available in Debian
> testing/unstable. I am planning to do the defaults change in mid August, around
> the time of the expected first GCC 9 point release (9.2.0).
> 
> There are only soname changes for rather unused shared libraries (libgo)
> involved, and the gnat defaults change will be handled separately by the Debian
> Ada maintainers.  The fortran module changes look ok according to Alastair
> McKinstry.
> 
> The gcc-9 package still ftbfs on kfreebsd-*.
> 
> We still have local patches for at least the various mips, kfreebsd and hurd

To be more exhaustive, for release architectures there are also patches
concerning the arm target and for other architectures patches concerning
the alpha, ia64 and sparc targets.

> targets.  Please forward these upstream and make sure that these are applied
> upstream.

The two MIPS libffi patches have been accepted upstream (i.e. in the
libffi git repository) 1.5 years ago for one and 4 years ago for the
other. I know there hasn't been any recent libffi release, so what can
be done to sync the gcc repository? Would it be possible to stop using
that outdated embedded copy and use the debian libffi package instead?

Aurelien
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.