Bug#982765: libffi: update symbols for nios2

Source: libffi Version: 3.3-5 Tags: patch User: helm...@debian.org Usertags: rebootstrap Please update symbols for nios2. I'm applying the relevant changes as a .debdiff. Helmut diff --minimal -Nru libffi-3.3/debian/changelog libffi-3.3/debian/changelog --- libffi-3.3/debian/changelog 2020-11-11

Bug#982760: gcc-11: ftbfs on mips64el due to ada problem

Package: src:gcc-11 Version: 11-20210207-1 Control: forward -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98996 s-pack96.adb should generate ldl/ldr pair + lwl/lwr pair since 96=64+32. When generate the pairs, it use the type SUBREG instead of REG, while in

Bug#972936: libgcc-s1 needs Breaks: libgcc1 (<< 1:10)

Thanks to bits from the RT. I can't reproduce this issue on a minimal installation, and the upgrade path has also been fixed #972820. -- Phil Morrell (emorrp1) ``` $ sudo sbuild-createchroot --command-prefix=eatmydata --include=eatmydata buster --chroot-prefix=temporary /srv/chroot/temporary

Processed: Re: Bug#916376 closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

Processing control commands: > reopen -1 Bug #916376 {Done: Debian FTP Masters } [src:gcc-8] gfortran-8-* has bad provides 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked

Bug#916376: closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

Control: reopen -1 Control: reassign -1 gfortran-11 On Sat, Feb 13, 2021 at 01:09:30PM +, Debian Bug Tracking System wrote: > as the package gcc-8 has just been removed from the Debian archive > unstable we hereby close the associated bug reports. We are sorry > that we couldn't deal with

Processed: Re: Bug#892281 closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

Processing control commands: > reopen -1 Bug #892281 {Done: Debian FTP Masters } [src:gcc-8] gcc: make PIE opt-out rather than opt-in 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No

Bug#892281: closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

Control: reopen -1 Control: reassign -1 src:gcc-11 On Sat, Feb 13, 2021 at 01:09:15PM +, Debian Bug Tracking System wrote: > as the package gcc-8 has just been removed from the Debian archive > unstable we hereby close the associated bug reports. We are sorry > that we couldn't deal with

Processed: Re: Bug#954831: Removed package(s) from unstable

Processing control commands: > reopen -1 Bug #735497 {Done: Debian FTP Masters } [libgcc1] libgcc1: Can switch to use new Allow-Internal-Symbol-Groups for aeabi symbols 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need

Bug#735497: Bug#954831: Removed package(s) from unstable

Control: reopen -1 Control: reassign -1 gcc-9,gcc-10,gcc-11 On Sat, 2021-02-13 at 13:07:12 +, Debian FTP Masters wrote: > Version: 1:8.4.0-7+rm > as the package gcc-8 has just been removed from the Debian archive > unstable we hereby close the associated bug reports. We are sorry > that we

Re: gcc-10-source cross build for xtensa with D enabled fails due to missing texi macro. patch included

On Sat, Feb 13, 2021 at 10:27:54AM +, Witold Baryluk wrote: > Have you had time to look at my MR draft I sent before? This fell off my radar because of the build problems due to not pulling in the extra required patches. I've done some cleanup of the package build so the extra Debian patches

Processed: Re: now in gcc-10

Processing commands for cont...@bugs.debian.org: > retitle 539912 gcc-*: for c99, POSIX requires that option -D have a lower > precedence than -U Bug #539912 [gcc-10] gcc-8: for c99, POSIX requires that option -D have a lower precedence than -U Changed Bug title to 'gcc-*: for c99, POSIX

Bug#539912: now in gcc-10

Control: reopen -1 Control: reassign -1 gcc-10 10.2.1-6 Still occurs there, which is now the default gcc. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP,

Processed: now in gcc-10

Processing control commands: > reopen -1 Bug #539912 {Done: Debian FTP Masters } [gcc-8] gcc-8: for c99, POSIX requires that option -D have a lower precedence than -U 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#972820: Distribution of Debian cannot be upgraded from Buster to Bullseye

Hi Phil, makes it sense to try a retest with the current Bullseye? Am 13.02.21 um 14:13 schrieb Phil Morrell: > Hi Karsten, I'm afraid I can't reproduce this issue on a minimal > installation, so either it's fixed or requires some other combination of > packages. > -- > Phil Morrell (emorrp1)

Processed: reopening 746426, reassign 746426 to gcc-11

Processing commands for cont...@bugs.debian.org: > reopen 746426 Bug #746426 {Done: Debian FTP Masters } [gcc-8] gcc: Enable -fasynchronous-unwind-tables on more arches. 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need

Bug#919577: closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

On Samstag, 13. Februar 2021 14:09:36 CET you wrote: > This is an automatic notification regarding your Bug report > which was filed against the g++-8 package: > > #919577: g++-8: Can't build GN tool due to bug in raw-string parsing > > It has been closed by Debian FTP Masters . > > Their

Bug#954831: Removed package(s) from unstable

Version: 1:8.4.0-7+rm Dear submitter, as the package gcc-8 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/954831 The

Bug#954831: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-8 |8.4.0-7 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x fixincludes | 1:8.4.0-7 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x

Bug#972820: Distribution of Debian cannot be upgraded from Buster to Bullseye

Hi Karsten, I'm afraid I can't reproduce this issue on a minimal installation, so either it's fixed or requires some other combination of packages. -- Phil Morrell (emorrp1) ``` $ sudo sbuild-createchroot --command-prefix=eatmydata --include=eatmydata buster --chroot-prefix=temporary

Bug#972820: marked as done (Distribution of Debian cannot be upgraded from Buster to Bullseye)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #972820, regarding Distribution of Debian cannot be upgraded from Buster to Bullseye to be marked as done. This means that you claim

Bug#964477: marked as done (Implicit conflict between libgcc1 and libgcc-s1 prevents upgrade)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #961990, regarding Implicit conflict between libgcc1 and libgcc-s1 prevents upgrade to be marked as done. This means that you claim

Bug#982425: marked as done (g++-8: aarch64 -ftree-vectorize generates wrong code)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #982425, regarding g++-8: aarch64 -ftree-vectorize generates wrong code to be marked as done. This means that you claim that the

Bug#961990: marked as done (Implicit conflict between libgcc1 and libgcc-s1 prevents upgrade)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #961990, regarding Implicit conflict between libgcc1 and libgcc-s1 prevents upgrade to be marked as done. This means that you claim

Bug#931182: marked as done (gcc-8: does not issue a warning with -Wall when a named enum value is overridden by a variable with the same name)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #931182, regarding gcc-8: does not issue a warning with -Wall when a named enum value is overridden by a variable with the same name

Bug#945991: marked as done (gcc-8 makes wrong integer comparison when using optimization flag)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #945991, regarding gcc-8 makes wrong integer comparison when using optimization flag to be marked as done. This means that you claim

Bug#932098: marked as done (gcc-8: LTO with -fdebug-prefix-map results in unreproducible build)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #932098, regarding gcc-8: LTO with -fdebug-prefix-map results in unreproducible build to be marked as done. This means that you claim

Bug#941911: marked as done (g++: Broken -x/suffix handling leads to spurious -Wc++-compat warnings)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #941911, regarding g++: Broken -x/suffix handling leads to spurious -Wc++-compat warnings to be marked as done. This means that you

Bug#921067: marked as done (libstdc++-8-dev: install fails with "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)")

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #921067, regarding libstdc++-8-dev: install fails with "dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)" to be

Bug#930012: marked as done (gcc-8: ICE building firefox 68.0~b6-2 on s390x and i386)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #930012, regarding gcc-8: ICE building firefox 68.0~b6-2 on s390x and i386 to be marked as done. This means that you claim that the

Bug#920022: marked as done (gfortran: doesn't generate reproducibly the same object file for an unchanged fortran source file)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #920022, regarding gfortran: doesn't generate reproducibly the same object file for an unchanged fortran source file to be marked as

Bug#929966: marked as done (g++-8: ICE (SIGILL in collect2) building musescore-snapshot on riscv64)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #929966, regarding g++-8: ICE (SIGILL in collect2) building musescore-snapshot on riscv64 to be marked as done. This means that you

Bug#918923: marked as done (gcc-8: why build an hppa64 cross-compiler on x32?)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #918923, regarding gcc-8: why build an hppa64 cross-compiler on x32? to be marked as done. This means that you claim that the problem

Bug#920582: marked as done (gcc -v --help prints some output to stderr, not just stdout)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #920582, regarding gcc -v --help prints some output to stderr, not just stdout to be marked as done. This means that you claim that

Bug#917115: marked as done (gcc-8: --fno-math-errno causes GCC to consider that malloc does not set errno)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #917115, regarding gcc-8: --fno-math-errno causes GCC to consider that malloc does not set errno to be marked as done. This means

Bug#919577: marked as done (g++-8: Can't build GN tool due to bug in raw-string parsing)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #919577, regarding g++-8: Can't build GN tool due to bug in raw-string parsing to be marked as done. This means that you claim that

Bug#914470: marked as done (gdc-8: ICE in gdc on call to defaulted alias template parameter that is a delegate literal)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #914470, regarding gdc-8: ICE in gdc on call to defaulted alias template parameter that is a delegate literal to be marked as done.

Bug#916376: marked as done (gfortran-8-* has bad provides)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #916376, regarding gfortran-8-* has bad provides to be marked as done. This means that you claim that the problem has been dealt with.

Bug#911599: marked as done (g++-8: removal of old abi mangling breaks compatibility with stretch)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #911599, regarding g++-8: removal of old abi mangling breaks compatibility with stretch to be marked as done. This means that you

Bug#915405: marked as done (gcc-8: Spurious stringop-overflow error when compiling with -O2)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #915405, regarding gcc-8: Spurious stringop-overflow error when compiling with -O2 to be marked as done. This means that you claim

Bug#911230: marked as done (gcc-8 : ICE on openmpi 3.1*)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #911230, regarding gcc-8 : ICE on openmpi 3.1* to be marked as done. This means that you claim that the problem has been dealt with.

Bug#913802: marked as done (g++-8: compilation crashing on lambda capturing aliased VLA)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #913802, regarding g++-8: compilation crashing on lambda capturing aliased VLA to be marked as done. This means that you claim that

Bug#892167: marked as done (gcc-8: go and libgo testsuites fails on amd64 (and other arches))

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #892167, regarding gcc-8: go and libgo testsuites fails on amd64 (and other arches) to be marked as done. This means that you claim

Bug#892281: marked as done (gcc: make PIE opt-out rather than opt-in)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #892281, regarding gcc: make PIE opt-out rather than opt-in to be marked as done. This means that you claim that the problem has been

Bug#735497: marked as done (libgcc1: Can switch to use new Allow-Internal-Symbol-Groups for aeabi symbols)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #735497, regarding libgcc1: Can switch to use new Allow-Internal-Symbol-Groups for aeabi symbols to be marked as done. This means

Bug#748298: marked as done (please drop the sjlj support)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #748298, regarding please drop the sjlj support to be marked as done. This means that you claim that the problem has been dealt with.

Bug#888951: marked as done (GCC bootstrap comparison failure build the D frontend on alpha)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #888951, regarding GCC bootstrap comparison failure build the D frontend on alpha to be marked as done. This means that you claim that

Bug#823778: marked as done (gcc-6: please make -mmusl return an error instead of doing the wrong thing)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #823778, regarding gcc-6: please make -mmusl return an error instead of doing the wrong thing to be marked as done. This means that

Bug#746426: marked as done (gcc: Enable -fasynchronous-unwind-tables on more arches.)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #746426, regarding gcc: Enable -fasynchronous-unwind-tables on more arches. to be marked as done. This means that you claim that the

Bug#539912: marked as done (gcc-8: for c99, POSIX requires that option -D have a lower precedence than -U)

Your message dated Sat, 13 Feb 2021 13:07:12 + with message-id and subject line Bug#954831: Removed package(s) from unstable has caused the Debian Bug report #539912, regarding gcc-8: for c99, POSIX requires that option -D have a lower precedence than -U to be marked as done. This means

Re: gcc-10-source cross build for xtensa with D enabled fails due to missing texi macro. patch included

Hi Jonathan. Have you had time to look at my MR draft I sent before? Cheers. On Fri, 22 Jan 2021 at 16:45, Witold Baryluk wrote: > > A simple (but not-too-simple) test is now included in MR: > > https://salsa.debian.org/electronics-team/toolchains/gcc-xtensa-lx106/-/merge_requests/1/diffs > >