preparing for GCC 4.9
With gcc-4.9 now available in testing, it is time to prepare for the change of
the default to 4.9, for a subset of architectures or for all (release)
architectures. The defaults for the gdc, gccgo, gcj and gnat frontends already
point to 4.9 and are used on all architectures. Issue #746805 tracks the
gfortran default change, including the change of the Fortran 90 module version
The Debian archive was rebuilt twice on amd64, once in February, resulting in
bug submissions for GCC and feedback for the porting guide , a second time in
March to file issues for packages failing to build with GCC 4.9 . Another
test rebuild for Ubuntu on amd64, i386, armhf, ppc64el didn't show any other
compiler regressions on these architectures.
I would like to see some partial test rebuilds (like buildd or minimal chroot
packages) for other architectures. Any possibility to setup such a test rebuild
for some architectures by the porters? Afaics the results for the GCC testsuite
look okish for every architecture.
I'll work on fixing the build failures in , help is of course appreciated.
Almost all build failures are analyzed and should be easy to fix (exceptions
e.g. #746883). Patches for the ones not caused by the Debian packaging may be
found in distributions already using GCC 4.9 as the default compiler (e.g.
If anything goes well, and a large amount of build failures are fixed, I plan to
make GCC 4.9 the default for the C/C++/ObjC/Obj-C++ frontends at the end of May,
beginning of June.
Bugs reports for packages building with a legacy version of GCC (4.6, 4.7, 4.8)
will be filed.