Current and upcoming toolchain changes for jessie

[Matthias Klose]

Hi,

GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters). I did not get
any feedback from other port maintainers, so unless this does change and port
maintainers get involved with toolchain maintenance, the architectures staying
at 4.6 or 4.7 shouldn't be considered for a successful release (re-)qualification.

| gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64
kfreebsd-i386 hurd-i386

no, they are probably not ok, and there surely are yet undiscovered regressions,
but at least the ARM porters did agree to address these. Same seems to be true
for the kfreebsd and hurd porters. They did change GCC defaults usually at the
same time as this was done for the x86 linux archs.

So the following would be the architectures for which some response is
requested urgently from port maintainers, to confirm they are ready for
Release arches: ia64 mips mipsel powerpc s390 s390x sparc
All the above have built gcc-4.8.1-2 or higher.

and nobody committing to scan the bts for architecture specific issues, nobody
to prepare test cases, nobody to forward these.

Other ports: alpha hppa* m68k powerpcspe ppc64 sh4* sparc64*
* these ports don't appear to have successfully built GCC 4.8 yet.

afaics, alpha, powerpcspe and ppc64 did build. Note that you cannot trust the
hppa status, this port is still denied access to ports.debian.org and is kept in
another place.

So yes, some of these ports are in better shape than the ports released with wheezy.

Matthias

[Thorsten Glaser]

I=E2=80=99d like to have gcj at 4.6 in gcc-defaults for m68k please,
until the 4.8 one stops FTBFSing.

please send a patch.

For gcc-defaults? I think that one is trivial=E2=80=A6

For gcj? I did not take Compiler Design in what two semesters
of Uni I managed until I ran out of money. I will, however,
forward #711558 to upstream.

I can=E2=80=99t do everything, but I don=E2=80=99t think anyone can accuse =
me
of not trying either=E2=80=A6

From me nothing against switching C/C++ to 4.8 for m68k at
this point, but I=E2=80=99d like to hear at least Wouter=E2=80=99s opini=

on

on that, and possibly Mikael since he=E2=80=99s not just doing work
upstream on gcc but also using it (for ColdFire) heavily.

same as well, please send a patch.

Wouter, Mikael: input on switching C/C++ to 4.8?

[ Ada ]

try it and send a patch please.

Would be useful to get it compiled first, for which #711558
is currently the blocker AFAICT. But I guess I=E2=80=99ll try eventually.

Note to myself: do not =E2=80=9Ctemporarily help out=E2=80=9D in any more D=
ebian
projects, you=E2=80=99ll never leave them=E2=80=A6

bye,
//mirabilos, sponsoring for a week of Linuxhotel would be nice=E2=80=A6
(I=E2=80=99m seriously short of hacking time, in general, recently,
and could use some switching of paper hangings for a while)
--=20
Support mksh as /bin/sh and RoQA dash NOW!
=E2=80=A3 src:bash (259 (278) bugs: 0 RC, 182 (196) I&N, 77 (82) M&W, 0 (0)=
F&P)
=E2=80=A3 src:dash (86 (102) bugs: 3 RC, 41 (46) I&N, 42 (53) M&W, 0 F&P)
=E2=80=A3 src:mksh (2 bugs: 0 RC, 0 I&N, 2 M&W, 0 F&P, 1 gift)
Loading Image... is pretty red, innit?

[Matthias Klose]

- The transition of gcc-4.8/libgcc1 to libunwind8.
- A removal of the libunwind7 dependency of around 4600 packages on ia64 - when
they are updated next time after the transition. The libc6.1 should (likely)
depend on libunwind8 after that in order to guarantee that libunwind8 is installed.

unless some ia64 porter steps up, it doesn't make sense to invest time into the
ia64 port. So better drop ia64 now, and don't bother with libunwind on ia64.

Matthias

[John David Anglin]

Hi Aurelien,

This is true that they have recently contacted me through another
email
address, but I haven't found time to work on that. Just stay tuned.

That's great news.

Helge and I have been working away as best we can to maintain the
port. I
know everybody is busy and this is a significant effort.

Dave
--
John David Anglin ***@bell.net

[Bastian Blank]

GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters).

GCC 4.8 seems fine on s390x, it can build a running Linux kernel. On
s390 something weird happened and I have to investigate what I broke.

Bastian
--
The face of war has never changed. Surely it is more logical to heal
than to kill.
-- Surak of Vulcan, "The Savage Curtain", stardate 5906.5

[Bastian Blank]

GCC 4.8 is now the default on all x86 architectures, and on all ARM
architectures (the latter confirmed by the Debian ARM porters).

Please change the default for s390 and s390x to 4.8.

Bastian