Bug#993337: gcc-11-base: changelog.Debian.gz multiarch inconsistency

Package: gcc-11-base Version: 11.2.0-3 Severity: normal Dear Maintainer, while upgrading other packages, I got Preparing to unpack .../0-gcc-11-base_11.2.0-3_mips64el.deb ... Unpacking gcc-11-base:mips64el (11.2.0-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-bFwhF7/0-gcc-11-base_

Bug#865690: cpp-7: Symlink liblto_plugin.so in /usr/lib/bfd-plugins

Package: cpp-7 Version: 7.1.0-7 Severity: normal Dear Maintainer, this package provides the plugin /usr/lib/gcc/x86_64-linux-gnu/7/liblto_plugin.so, which is good (not sure why it is in package cpp-7 in particular, but I don't care as long as it is available). However, binutils look for plugi

Bug#619963: testcase

Hello, in the prototype of memmove (taken from glibc bits/string3.h), you will notice __restrict in front of the arguments. This is not present in more recent glibc versions and is a likely cause of your trouble. -- Marc Glisse -- To UNSUBSCRIBE, email to debian-gcc-requ

Bug#365039: gcc: c99 calls cc expecting it to be gcc

Package: gcc Version: 4.0.2-2 Severity: minor The c99 script executes "cc -std=c99". But in debian, cc is chosen by the alternatives mechanism, and may be a symlink for tcc, which does not understand this option. It might be safer to call gcc instead of cc. By the way, reportbug was refusing to l