Re: preparing for GCC 4.9
Yunqiang Su <[email protected]>
| Newsgroups | gmane.linux.debian.ports.amd64 |
|---|---|
| Message-ID | <CAKcpw6Ve=nBETYywGW+QM99BOhki2q+1dVxW6fZAzFNa9Wc2Sg__24677.8740118772$1399563313$gmane$org@mail.gmail.com> |
On Thu, May 8, 2014 at 11:25 PM, Matthias Klose <[email protected]> wrote: > 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 > change. > > The Debian archive was rebuilt twice on amd64, once in February, resulting in > bug submissions for GCC and feedback for the porting guide [1], a second time in > March to file issues for packages failing to build with GCC 4.9 [2]. 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 set a build farm with gcc-4.9 for mips64el. It works well: it has no more failures than your amd64 one. All the buildlogs can be found in http://mips.wicp.net:9998/mips2/buildlog/ I noticed ctpp2 failed due to symbols problems on both amd64(pbuilder) and mips64el(sbuild). It seems that you didn't report bug on it. > > I'll work on fixing the build failures in [2], 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. > Fedora 21). > > 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. > > Matthias > > [1] http://gcc.gnu.org/gcc-4.9/porting_to.html > [2] > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-4.9;[email protected] > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: https://lists.debian.org/[email protected] > -- Yunqiang Su