Processed: Re: Bug#1101749 closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1101749: fixed in gcc-15 15-20250406-1)

cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions gcc-15/15-20250406-1. -- 1101749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1063664 closed by Matthias Klose (no feedback, closing this issue)

Processing control commands: > reopen -1 Bug #1063664 {Done: Matthias Klose } [gnat-13-aarch64-linux-gnu,gnat-13-arm-linux-gnueabihf,gnat-13-i686-linux-gnu,gnat-13-powerpc64le-linux-gnu,gnat-13-riscv64-linux-gnu,gnat-13-s390x-linux-gnu] gcc-13-cross: file conflicts between gnat-13- and gnat-{9,

Processed: Re: Bug#1102350: libstdc++-15-dev: libstdc++-modules.json points at wrong location (was: cmake 4.0 couldn't find correct std module source file)

Processing control commands: > reassign 1102350 libstdc++-15-dev Bug #1102350 [cmake] cmake 4.0 couldn't find correct std module source file Bug reassigned from package 'cmake' to 'libstdc++-15-dev'. No longer marked as found in versions 4.0.0. Ignoring request to alter fixed versions of bug #1102

Re: Processed: mass reassign

this feels so wrong ... please fix #1092484 instead. It's perfectly fine to rely on glibc's iconv support. There's no other distro besides Debian still insisting on building libxml2 explicitly with ICU. Matthias On 26.03.25 01:03, Debian Bug Tracking System wrote: Processing commands for

Processed: Re: Bug#1100805: gcc-14 version 14.2.0-18 causes glibc to be miscompiled on armhf

Processing control commands: > clone -1 -2 Bug #1100805 [gcc-14] gcc-14 version 14.2.0-18 causes glibc to be miscompiled on armhf Bug 1100805 cloned as bug 1100939 > reassign -2 src:libinsane Bug #1100939 [gcc-14] gcc-14 version 14.2.0-18 causes glibc to be miscompiled on armhf Bug reassigned fr

Processed: Re: Bug#1100805: gcc-14 version 14.2.0-18 causes glibc to be miscompiled on armhf

Processing control commands: > clone -1 -2 Bug #1100805 [gcc-14] gcc-14 version 14.2.0-18 causes glibc to be miscompiled on armhf Bug 1100805 cloned as bug 1100821 > reassign -2 src:glibc Bug #1100821 [gcc-14] gcc-14 version 14.2.0-18 causes glibc to be miscompiled on armhf Bug reassigned from p

Processed: Re: Bug#1099646: transition: gnat

Processing control commands: > block -1 by 1096181 1100460 1100461 Bug #1099646 [release.debian.org] transition: gnat 1099646 was not blocked by any bugs. 1099646 was not blocking any bugs. Added blocking bug(s) of 1099646: 1100460, 1096181, and 1100461 -- 1099646: https://bugs.debian.org/cgi-bi

Re: Bug#1096423: cenon.app: ftbfs with GCC-15

Control: clone -1 -2 Control: reassign -2 gobjc-15 15-20250220-1 Control: retitle -2 Implementation of "if declarations" makes instance variables unknown under certain conditions Control: forwarded -2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119117 Control: block -1 with -2 On Mon, 17 Feb 202

Processed: Re: Bug#1096423: cenon.app: ftbfs with GCC-15

Processing control commands: > clone -1 -2 Bug #1096423 [src:cenon.app] cenon.app: ftbfs with GCC-15 Bug 1096423 cloned as bug 1099541 > reassign -2 gobjc-15 15-20250220-1 Bug #1099541 [src:cenon.app] cenon.app: ftbfs with GCC-15 Bug reassigned from package 'src:cenon.app' to 'gobjc-15'. No longer

Processed: Re: Bug#1094828: g++ internal compiler error on arm64 when compiling pytorch

Processing control commands: > tags -1 + moreinfo Bug #1094828 [g++-14] g++ internal compiler error on arm64 when compiling pytorch Ignoring request to alter tags of bug #1094828 to the same tags previously set -- 1094828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094828 Debian Bug Tra

Processed: Re: Bug#1083135: gcc-14-aarch64-linux-gnu: cross compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"

Processing control commands: > retitle -1 gcc-VER-TRIPLET may use binutils for a different architecture Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'" Changed Bug title to 'gcc-VER-TRIPLET may

Processed: Re: Bug#1094828: g++ internal compiler error on arm64 when compiling pytorch

Processing control commands: > reopen -1 Bug #1094828 {Done: Matthias Klose } [g++-14] g++ internal compiler error on arm64 when compiling pytorch Bug reopened Ignoring request to alter fixed versions of bug #1094828 to the same values previously set -- 1094828: https://bugs.debian.org/cgi-bin

Processed: Re: Bug#1086679: gfortran-for-host should provide libgfortran.so on a default library path

Processing control commands: > tags -1 + moreinfo Bug #1086679 [gfortran-14-for-host] gfortran-for-host should provide libgfortran.so on a default library path Added tag(s) moreinfo. -- 1086679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086679 Debian Bug Tracking System Contact ow...@b

Processed: Re: Bug#1094828: g++ internal compiler error on arm64 when compiling pytorch

Processing control commands: > tags -1 + moreinfo Bug #1094828 [g++-14] g++ internal compiler error on arm64 when compiling pytorch Added tag(s) moreinfo. -- 1094828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1093151: closed by Matthias Klose (Re: Bug#1093151: libn32gcc-14-dev: Not installable on mips64el)

On 17.01.25 01:06, Adrian Bunk wrote: On Wed, Jan 15, 2025 at 07:21:02PM +, Debian Bug Tracking System wrote: ... Version: 14.2.0-14 On 15.01.25 19:31, Andrey Rakhmatullin wrote: Package: libn32gcc-14-dev Version: 14.2.0-13 Unless I'm very confused, libn32gcc-14-dev is not installable on

Bug#1093151: closed by Matthias Klose (Re: Bug#1093151: libn32gcc-14-dev: Not installable on mips64el)

On Wed, Jan 15, 2025 at 07:21:02PM +, Debian Bug Tracking System wrote: >... > Version: 14.2.0-14 > > On 15.01.25 19:31, Andrey Rakhmatullin wrote: > > Package: libn32gcc-14-dev > > Version: 14.2.0-13 > > > > Unless I'm very confused, libn32gcc-14-dev is not installable on mips64el > > and th

Processed: Re: Bug#1084066: amdgcn-tools: Please upgrade build-dep to llvm/clang 18 or 19

Processing control commands: > clone -1 -2 Bug #1084066 [src:amdgcn-tools] amdgcn-tools: Please upgrade build-dep to llvm/clang 18 or 19 Bug 1084066 cloned as bug 1092643 1081250 was blocked by: 1084065 1084066 1084067 1084068 1084069 1084070 1084071 1084072 1084073 1084074 1084075 1084076 10840

Processed: Re: Bug#1092181: cpp-11 and cpp-11-x86-64-linux-gnu have an undeclared cross-architecture file conflict

Processing control commands: > severity -1 important Bug #1092181 [cpp-11,cpp-11-x86-64-linux-gnu] cpp-11 and cpp-11-x86-64-linux-gnu have an undeclared cross-architecture file conflict Severity set to 'important' from 'serious' -- 1092181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092

Processed: Re: Bug#1092181: cpp-11 and cpp-11-x86-64-linux-gnu have an undeclared cross-architecture file conflict

Processing control commands: > severity -1 important Bug #1092182 [cpp-12,cpp-12-x86-64-linux-gnu] cpp-12 and cpp-12-x86-64-linux-gnu have an undeclared cross-architecture file conflict Severity set to 'important' from 'serious' -- 1092182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092

Processed: Re: fixed

, and you may need to re-add them. Bug reopened No longer marked as fixed in versions 2.43.50.20241004-1. -- 1067665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Re: Bug#1090345: fix for PR ada/117996 causes a change for the gnat-13- provides

On 17.12.24 23:13, Nicolas Boulenguez wrote: However, I see that you have reverted the fix for PR ada/117996 from libgnat-13, and it make sense to only apply it to gcc-13 after the gnat-14 transition.. It will then affect Ada libraries neither in bookworm backports (gnat-12) nor in trixie (gnat-

Processed: Re: Bug#1089007: sbuild: unshare backend fails to build gcc since version 0.86.0

Processing control commands: > reassign -1 src:gcc-14 Bug #1089007 [sbuild] sbuild: unshare backend fails to build gcc since version 0.86.0 Bug reassigned from package 'sbuild' to 'src:gcc-14'. No longer marked as found in versions sbuild/0.86.0. Ignoring request to alter fixed versions of bug #1

Re: Bug#1088262: python-apt: ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmm

t checkout 2.9.14 Previous HEAD position was de7c78680 Release 2.9.4 HEAD is now at 1a03ebc11 Release 2.9.14 root@2540807186ac:/build/apt# ninja -C obj-x86_64-linux-gnu/ apt-pkg ninja: Entering directory `obj-x86_64-linux-gnu/' [0/1] Re-running CMake... -- Performing Test have-compiler-flag:-Wp,-D

Processed (with 1 error): Re: Bug#1088262: python-apt: ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_trai

Processing control commands: > clone -1 -2 -3 Bug #1088262 [src:python-apt] python-apt: ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm Bug 1088262 cloned as bugs 1088

Re: Bug#1088262: python-apt: ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmm

On Mon, Nov 25, 2024 at 06:59:49PM -0800, Otto Kekäläinen wrote: > Source: python-apt > Version: 2.9.1 > Severity: serious > > Seems the latest version of python-apt has some serious regressions as > https://tracker.debian.org/pkg/python-apt shows wide-spread > autopkgtest failures. > > In a clea

Processed: Re: Bug#1088093: gcc-14-offload-nvptx: offload to nvptx-none completely broken

Processing control commands: > reassign -1 nvptx-tools Bug #1088093 [gcc-14-offload-nvptx] gcc-14-offload-nvptx: offload to nvptx-none completely broken Bug reassigned from package 'gcc-14-offload-nvptx' to 'nvptx-tools'. No longer marked as found in versions gcc-14/14.2.0-8. Ignoring request to

Re: Updates to the trixie freeze policy

On 02.11.24 18:35, Sebastian Ramacher wrote: Dear toolchain, debian-installer, and image maintainers, We, as the release team, are aware that we are late with the announcement of the freeze timeline for trixie. After some internal discussions on how we want to handle the freeze for trixie based

Processed: Re: Bug#1086791: lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant

Processing control commands: > severity -1 important Bug #1086791 [src:lziprecover] lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant Severity set to 'important' from 'serious' > reassign -1 gcc-14 Bug #1086791 [src:lziprecover] lziprecover: FTBFS on riscv64 due to out-of-b

Re: Bug#1086791: lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant

control: severity -1 important control: reassign -1 gcc-14 control: retitle -1 gcc: riscv64 backend emits large relocations due to loop strength reduction control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117460 control: affects -1 lziprecover On 2024-11-05 21:47, Jessica Clarke

Re: How to deal with gfortran dependencies?

Hi Drew, On Sat, Nov 02, 2024 at 05:14:31PM +0100, Drew Parsons wrote: > It seems to me there's the proverbial elephant in the room if we're > discussing improving cross-compilation compiler dependency definitions, and > that's the MPI compiler wrapper mpicc/mpicxx/mpifort. > > Most of the packag

Re: Updates to the trixie freeze policy

Hi, Sebastian Ramacher (2024-11-02): > Dear toolchain, debian-installer, and image maintainers, > > We, as the release team, are aware that we are late with the > announcement of the freeze timeline for trixie. After some internal > discussions on how we want to handle the freeze for trixie base

Re: How to deal with gfortran dependencies?

On 2024-11-02 14:55, Matthias Klose wrote: A lot of the fortran packing, including the module provisions were suggested and are maintained (?) by other Debian developers, some of them from the science team. It would make sense to include these people into the discussions as well. Thanks Matt

Bug#1086120: marked as done (gcc-14: Please re-enable rs on hurd-i386 and hurd-amd64)

Your message dated Sat, 02 Nov 2024 15:34:31 + with message-id and subject line Bug#1086120: fixed in gcc-14 14.2.0-8 has caused the Debian Bug report #1086120, regarding gcc-14: Please re-enable rs on hurd-i386 and hurd-amd64 to be marked as done. This means that you claim that the problem

Re: How to deal with gfortran dependencies?

A lot of the fortran packing, including the module provisions were suggested and are maintained (?) by other Debian developers, some of them from the science team. It would make sense to include these people into the discussions as well. On 31.10.24 17:45, Helmut Grohne wrote: Hi fellow cros

Processed: Re: Bug#1080974: kf6-ktexttemplate: FTBFS on arm64 with gcc-14 and optimization level 2

Processing control commands: > tags -1 + fixed-upstream Bug #1080974 [gcc-14] gcc-14: regression on arm64, wrong code at -O2 with late pair fusion pass Added tag(s) fixed-upstream. -- 1080974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080974 Debian Bug Tracking System Contact ow...@bug

RE: Autopkgtest support for libelf1 source package

Hello, This is a gentle reminder to my previous mail regarding autopkgtest support for the package. Or would like to understand If I have to contact someone else for such details. Basically, CIP (Civil Infrastructure Platform Project) aims to provide SLTS (Super Long Term Support) to selected

RE: Autopkgtest support for libffi8 source package

Hello, This is a gentle reminder to my previous mail regarding autopkgtest support for the package. Or would like to understand If I have to contact someone else for such details. Basically, CIP (Civil Infrastructure Platform Project) aims to provide SLTS (Super Long Term Support) to selected

Bug#1086120: gcc-14: Please re-enable rs on hurd-i386 and hurd-amd64

Package: gcc-14 Version: 14.2.0-7 Severity: normal Tags: patch Hello, cargo/rustc are available both on hurd-i386 and hurd-amd64, and gccrs builds fine there, could you re-enable building it as the attached patch does? Thanks, Samuel -- System Information: Debian Release: trixie/sid APT

Processed: Re: gcc-14-aarch64-linux-gnu: cross compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"

Processing control commands: > severity -1 normal Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'" Severity set to 'normal' from 'serious' > tags -1 + moreinfo Bug #1083135 [gcc-14-aarch64-linux-

Processed: Re: gcc-14-aarch64-linux-gnu: cross compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'"

Processing control commands: > severity -1 normal Bug #1083135 [gcc-14-aarch64-linux-gnu] gcc-14-aarch64-linux-gnu: cross compiler 'aarch64-linux-gnu-gcc' always error: "as: unrecognized option '-EL'" Ignoring request to change severity of Bug 1083135 to the same value. > tags -1 + moreinfo Bug #

Processed: Re: Bug#1082125: vim: FTBFS on s390x: Test_glob2regpat_valid line 8: Expected '.*' but got '$'

Processing control commands: > reassign -1 gcc-14 14.1.0-1 Bug #1082125 [src:vim] vim: FTBFS on s390x: Test_glob2regpat_valid line 8: Expected '.*' but got '$' Bug reassigned from package 'src:vim' to 'gcc-14'. No longer marked as found in versions vim/2:9.1.0709-1 and vim/2:9.1.0698-1. Ignoring

Re: Bug#1082125: vim: FTBFS on s390x: Test_glob2regpat_valid line 8: Expected '.*' but got '$'

Control: reassign -1 gcc-14 14.1.0-1 Control: retitle -1 gcc-14: miscompiles code on s390x at -O2 Control: tag -1 upstream Control: severity -1 normal Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116799 On Wed, Sep 18, 2024 at 02:40:11PM GMT, James McCoy wrote: > On Wed, Sep

Processed: Re: RFS: gcc-doc uploads

Processing control commands: > owner -1 ! Bug #1078158 [src:gcc-doc-defaults] gcc-doc-defaults: switch to GCC 14 Owner recorded as Soren Stoutner . -- 1078158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: libquadmath0: wrongly assumes that the storage for __float128 arguments is aligned

Processing control commands: > notfixed -1 libquadmath0/14-20240429-1 Bug #1076612 {Done: Aurelien Jarno } [libquadmath0] libquadmath0: wrongly assumes that the storage for __float128 arguments is aligned The source libquadmath0 and version 14-20240429-1 do not appear to match any binary packag

Processed: Re: Bug#1073932: libstdc++-14-dev: 'using' specification results in compiler error when specifying -fmodules-ts

Processing control commands: > tags -1 + moreinfo Bug #1073932 [libstdc++-14-dev] libstdc++-14-dev: 'using' specification results in compiler error when specifying -fmodules-ts Added tag(s) moreinfo. -- 1073932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073932 Debian Bug Tracking Syste

Processed: Re: Bug#1073925: libstdc++-14-dev: Using multiple import statements generates an internal compiler error

Processing control commands: > tags -1 + moreinfo Bug #1073925 [libstdc++-14-dev] libstdc++-14-dev: Using multiple import statements generates an internal compiler error Added tag(s) moreinfo. -- 1073925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073925 Debian Bug Tracking System Conta

Processed: Re: gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el

Processing control commands: > fixed -1 gcc-14/14.1.0-1 Bug #1004184 [src:gcc-11] gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el Marked as fixed in versions gcc-14/14.1.0-1. -- 1004184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004184 Debian Bug Tracking System Conta

Processed: Re: Bug#1077657: Acknowledgement (g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O)

Processing control commands: > found -1 14.2.0-2 Bug #1077657 [g++-14-arm-linux-gnueabihf] g++-14-arm-linux-gnueabihf: Forward declaration of std::vector does not compile with -O Marked as found in versions gcc-14/14.2.0-2. -- 1077657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077657 D

Processed: Re: Bug#1078144: marked as done (gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found)

Processing control commands: > reopen -1 Bug #1078144 {Done: Matthias Klose } [src:gcc-14] gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need t

Processed: Re: Bug#1078144: gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found

Processing control commands: > tags -1 + pending Bug #1078144 [src:gcc-14] gcc-14: FTBFS: /bin/bash: line 1: gnatmake: command not found Added tag(s) pending. -- 1078144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078144 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

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

cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions 9.5.0-6+rm. > reassign -1 libgcc-s1 Bug #735497 [gcc-9,gcc-10,gcc-11] libgcc1: Can switch to use new Allow-Internal-Symbol-Groups for aeabi symbols Bug reassigned from package 'gcc-9,gcc-10,

Re: Bug#735497 closed by Debian FTP Masters (Bug#1076502: Removed package(s) from unstable)

Control: reopen -1 Control: reassign -1 libgcc-s1 On Sun, 2024-07-28 at 15:30:09 +, Debian Bug Tracking System wrote: > Version: 9.5.0-6+rm > > Dear submitter, > > as the package gcc-9 has just been removed from the Debian archive > unstable we hereby close the associated bug reports. We ar

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

Processing control commands: > reopen -1 Bug #930430 {Done: Debian FTP Masters } [libasan5] libasan5: AddressSanitizer breaks when LD_PRELOAD is defined 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need t

Re: Bug#1075573: tightvnc: ftbfs with GCC-14

Hello debian-gcc team, On Fri, 2024-07-05 at 23:48 +0200, Sven Geuer wrote: > On Wed, 2024-07-03 at 12:46 +, Matthias Klose wrote: > > > Package: src:tightvnc > > Version: 1:1.3.10-8 > > [...] > > Please keep the issue open until the package can be built in > > a follow-up test rebuild. I wo

Processed: Re: Bug#998802: which deprecated

Processing commands for cont...@bugs.debian.org: > fixed 998802 elfutils/0.187-2 Bug #998802 [libdebuginfod-common] which deprecated Marked as fixed in versions elfutils/0.187-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 998802: https://bugs.debian.org/cgi-b

Processed: Re: Bug#1063768: debuginfod: man page gives an outdated equivalent of -U

Processing commands for cont...@bugs.debian.org: > fixed 1063768 elfutils/0.191-1 Bug #1063768 [debuginfod] debuginfod: man page gives an outdated equivalent of -U Marked as fixed in versions elfutils/0.191-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 10637

Processed: Re: gcc-13 FTCBFS: target system type set to nvptx-unknown-none

Processing control commands: > retitle -1 gcc-13 FTCBFS: nvptx does not cross compile Bug #1060075 [src:gcc-13] gcc-13 FTCBFS: target system type set to nvptx-unknown-none Changed Bug title to 'gcc-13 FTCBFS: nvptx does not cross compile' from 'gcc-13 FTCBFS: target system type set to nvptx-unkn

Processed: Re: Bug#1069066: LIMITS_H_TEST is frequently wrong on Debian

Processing control commands: > tags -1 - patch Bug #1069066 [src:gcc-14] LIMITS_H_TEST is frequently wrong on Debian Removed tag(s) patch. -- 1069066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1067087: GCC is not the place to enable frame pointers

Processing commands for cont...@bugs.debian.org: > reopen 1067087 Bug #1067087 {Done: Matthias Klose } [src:gcc-14] GCC frame pointers Bug reopened Ignoring request to alter fixed versions of bug #1067087 to the same values previously set > reassign 1067087 dpkg-dev Bug #1067087 [src:gcc-14] GCC

Processed: Re: Bug#1063664: gcc-13-cross: file conflicts between gnat-13- and gnat-{9,10}-

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was hel...@subdivi.de). > usertags 1063664 + fileconflict There were no usertags set. Usertags are now: fileconflict. > reassign 1063664 > gnat-13-aarch64-linux-gnu,gnat-

Processed: Re: Bug#1067453: gnat: Ada.Calendar.Clock crashes on time_t64 architectures

Processing control commands: > forwarded -1 https://gcc.gnu.org/PR114424 Bug #1067453 [gnat-13] gnat: Ada.Calendar.Clock crashes on time_t64 architectures Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR114424'. -- 1067453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067453 Debian

Processed: Re: Bug#1066891: gcc-13: ICE compiling OpenSSH: in change_address_1

Processing control commands: > forwarded -1 https://gcc.gnu.org/PR114358 Bug #1066891 [src:gcc-13] gcc-13: ICE compiling OpenSSH: in change_address_1 Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR114358'. -- 1066891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066891 Debian Bug T

Processed: Re: gcc-13: ICE compiling OpenSSH: in change_address_1

Processing commands for cont...@bugs.debian.org: > tags 1066891 - moreinfo Bug #1066891 [src:gcc-13] gcc-13: ICE compiling OpenSSH: in change_address_1 Removed tag(s) moreinfo. > found 1066891 13.2.0-18 Bug #1066891 [src:gcc-13] gcc-13: ICE compiling OpenSSH: in change_address_1 Marked as found in

Processed: Re: Processed: gcc-13: ICE compiling OpenSSH: in change_address_1

Processing control commands: > tags -1 + moreinfo Bug #1066891 [src:gcc-13] gcc-13: ICE compiling OpenSSH: in change_address_1 Added tag(s) moreinfo. -- 1066891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1066849: Re: Bug#1066849: libelf1 Version mismatch (0.190-1+b1 vs 0.191-1)

Hello, Thanks for the info. So this may be linked to ? Do you know where I can find information about the time_t64 transition?

Processed: Re: libdebuginfod1t64 dependency problem breaks the upgrade

Processing control commands: > retitle -1 libdebuginfod1t64 dependency problem makes dpkg fail with attempt > of removal of libdebuginfod-common Bug #1065603 [libdebuginfod1t64] libdebuginfod1t64 dependency problem breaks the upgrade Changed Bug title to 'libdebuginfod1t64 dependency problem mak

Re: timet64 ABI change for ports architectures

[resending to debian-ports, I didn't see this mail in the mail archives for the architectures] probematic arch currently is hppa, where both gcc-13 and gcc-14 builds are ftbfs. see the logs from experimental. On 20.02.24 05:09, Matthias Klose wrote: We'll hard-code the -D_TIME_BITS=64 setting

Processed: Re: Bug#1063882: gcc: Internal error from ternary cond as inline asm parameter

Processing control commands: > tags -1 + moreinfo Bug #1063882 [gcc] gcc: Internal error from ternary cond as inline asm parameter Added tag(s) moreinfo. -- 1063882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Re: Bug#1062354: libatomic1: 14-20240127-1 missing libat_test_and_set_1_i2

Processing control commands: > severity 1061370 grave Bug #1061370 [src:gcc-14] gcc-14 ftbfs on armel Severity set to 'grave' from 'important' > forcemerge -1 1061370 Bug #1062354 [libatomic1] libatomic1: 14-20240127-1 missing libat_test_and_set_1_i2 Unable to merge bugs because: package of #1061

Processed: Re: Bug#1061370: gcc-14 ftbfs on armel

Processing control commands: > tags -1 patch Bug #1061370 [src:gcc-14] gcc-14 ftbfs on armel Added tag(s) patch. -- 1061370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1061370: gcc-14 ftbfs on armel

Processing control commands: > affects -1 systemd Bug #1061370 [src:gcc-14] gcc-14 ftbfs on armel Added indication that 1061370 affects systemd -- 1061370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: gm2-14: typo in title in gm2-14 package claiming being D compiler, not modula

Processing control commands: > tags 1061372 + patch Bug #1061372 [gm2-14] gm2-14: typo in title in gm2-14 package claiming being D compiler, not modula Added tag(s) patch. -- 1061372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061372 Debian Bug Tracking System Contact ow...@bugs.debian.

gcc displaying bullshit allocation numbers? (was: Re: Ability to further support 32bit architectures)

Hi On Thu, Jan 11, 2024 at 10:25:39AM +0100, Bastian Blank wrote: > Linux 6.7 fails to build on at least i386 and armhf. Even it now > manages to make the compiler fail to allocate memory: > | cc1: out of memory allocating 135266296 bytes after a total of 235675648 > bytes I just tried to find

Processed: Re: gcc-13: Please build gcc with -mbranch-protection=standard to fix PAC/BTI support on arm64

Processing control commands: > tags -1 + moreinfo Bug #1057469 [gcc-12] gcc-12: Please build with -mbranch-protection=standard to enable PAC/BTI support on arm64 Ignoring request to alter tags of bug #1057469 to the same tags previously set -- 1057469: https://bugs.debian.org/cgi-bin/bugreport.

Processed: Re: gcc-13: Please build gcc with -mbranch-protection=standard to fix PAC/BTI support on arm64

Processing control commands: > tags -1 + moreinfo Bug #1057469 [gcc-12] gcc-12: Please build with -mbranch-protection=standard to enable PAC/BTI support on arm64 Added tag(s) moreinfo. -- 1057469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057469 Debian Bug Tracking System Contact ow...

Processed: Re: libmpfr6: major formatted output function bugs with %c and the value 0

Processing control commands: > tags -1 fixed-upstream Bug #1057355 [libmpfr6] libmpfr6: major formatted output function bugs with %c and the value 0 Added tag(s) fixed-upstream. -- 1057355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057355 Debian Bug Tracking System Contact ow...@bugs.d

Re: Enabling PAC/BTI support on arm64

Hey Aurelien, On 2023-12-05 08:32, Aurelien Jarno wrote: > What about the patch below, it basically just change the compiler to > always enable -mbranch-protection=standard, and it's also used for the > configure script. > --- glibc-2.37/debian/sysdeps/arm64.mk > +++ glibc-2.37/debian/sysdeps/arm

Re: Enabling PAC/BTI support on arm64

Hi Emanuele, On 2023-12-04 16:13, Emanuele Rocca wrote: > Hello Aurelien, > > On 2023-12-03 01:08, Aurelien Jarno wrote: > > On 2023-11-29 09:56, Emanuele Rocca wrote: > > > To add BTI to the NOTE section of the above, we would need to build both > > > GCC and glibc with -mbranch-protection=stand

Re: Enabling PAC/BTI support on arm64

Hello Aurelien, On 2023-12-03 01:08, Aurelien Jarno wrote: > On 2023-11-29 09:56, Emanuele Rocca wrote: > > To add BTI to the NOTE section of the above, we would need to build both > > GCC and glibc with -mbranch-protection=standard. For gcc-13 I have > > proposed https://bugs.debian.org/1055711.

Re: Enabling PAC/BTI support on arm64

Hi Emanuele, On 2023-11-29 09:56, Emanuele Rocca wrote: > Hi! > > I would like to ask for suggestions about the best way to enable PAC/BTI > support in glibc and GCC on Debian. > > PAC and BTI are two useful Arm security features, see this recent > presentation at the Mini Debconf for all detail

Bug#1050429: GCC 13 stopped supporting a documented option (was Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL')

On 2023-11-24 18:58 +, Thorsten Glaser wrote: > Unfortunately, eller is down Eller had to move hosting provider at short notice. It is now racked again but needs network configuration for new location. It will hopefully re-appear by end-Monday. Wookey -- Principal hats: Debian, Wookw

Bug#1050429: GCC 13 stopped supporting a documented option (was Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL')

n terminated. | % mips64el-linux-gnuabi64-gcc | mips64el-linux-gnuabi64-gcc: fatal error: no input files | compilation terminated. Now, what is the problem? Well, the spec removes the knowledge about the -EL and -EB arguments by overriding *cc1. So the fix is to re-add those arguments: | %rename cc1 ol

Bug#1050429: GCC 13 stopped supporting a documented option (was Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL')

Matthias Klose dixit: > you can work around it Unfortunately not. (The musl packagers might be able to.) >, this is not an RC issue. Please stop playing > bug ping pong. If GCC stops supporting an option it used to support, and where the GCC documentation say it’s supported, it in my opinion ve

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

Processing control commands: > severity -1 normal Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'normal' from 'serious' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug Track

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

Processing control commands: > severity -1 serious Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'serious' from 'normal' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug Trac

Processed: Re: Bug#1055711: gcc-13: Please build gcc with -mbranch-protection=standard to fix PAC/BTI support on arm64

Processing control commands: > tags -1 + moreinfo Bug #1055711 [gcc-13] gcc-13: Please build gcc with -mbranch-protection=standard to fix PAC/BTI support on arm64 Added tag(s) moreinfo. -- 1055711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055711 Debian Bug Tracking System Contact ow..

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

Processing control commands: > severity -1 normal Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'normal' from 'serious' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug Track

Processed: Re: Bug#1056238: gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity

Processing control commands: > tags -1 + moreinfo Bug #1056238 [src:gcc-13] gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) moreinfo. -- 1056238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056238 Debian Bug Tracking System Contact

Processed (with 1 error): Re: Bug#1055750: Bug#1055228: plplot: FTBFS on armhf (test segfault)

Processing control commands: > reassign -1 plplot Bug #1055750 [gfortran] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Bug reassigned from package 'gfortran' to 'plplot'. No longer marked as found in versions 13.2.0-1. Ignoring request to alter fixed versions of bug

Processed: Re: Bug#1055228: plplot: FTBFS on armhf (test segfault)

Processing control commands: > forwarded -1 https://sourceforge.net/p/plplot/bugs/206/ Bug #1055750 [gfortran] gfortran: [armhf] Yield SIGBUS when compiling with -fstack-clash-protection Set Bug forwarded-to-address to 'https://sourceforge.net/p/plplot/bugs/206/'. -- 1055750: https://bugs.debia

Re: gcc-multilib & g++-multilib issues

Please stop filing duplicating bogus reports.  You make unproven claims without giving any rationale. On 14.11.23 00:04, jahway-bug-reports wrote: Hi Matthias, There is software which will not build natively on Debian 10/11/12 without the gcc-multilib & g++-multilib packages https://packages

Processed: Re: Bug#1053405: darktable: FTBFS on arm64 (gcc bug?)

Processing control commands: > reassign -1 src:gcc-13 Bug #1053405 [src:darktable] darktable: FTBFS on arm64 (gcc bug?) Bug reassigned from package 'src:darktable' to 'src:gcc-13'. No longer marked as found in versions darktable/4.4.2-1. Ignoring request to alter fixed versions of bug #1053405 to

Processed: Re: libquadmath (gcc): license may be inaccurate

Processing control commands: > reassign 1052314 libquadmath0 Bug #1052314 [libquadmath] libquadmath (gcc): license may be inaccurate Warning: Unknown package 'libquadmath' Bug reassigned from package 'libquadmath' to 'libquadmath0'. No longer marked as found in versions libquadmath0. Ignoring requ

Processed: Re: Bug#1050013: gcc-13: Please don't build the Ada, Go, D and M2 on LoongArch

Processing control commands: > tags -1 - moreinfo Bug #1050013 [gcc-13] gcc-13: Please don't build the Ada, Go, D and M2 on LoongArch Removed tag(s) moreinfo. -- 1050013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050013 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Processed: Re: aarch64: Miscompilation at O1 level (O0 is working)

Processing control commands: > tags -1 + moreinfo Bug #1050933 [g++-13] aarch64: Miscompilation at O1 level (O0 is working) Added tag(s) moreinfo. -- 1050933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: False positive -Warray-bounds warning

Processing control commands: > tags -1 + moreinfo Bug #1041607 [libstdc++-13-dev] False positive -Warray-bounds warning Added tag(s) moreinfo. -- 1041607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

Processing commands for cont...@bugs.debian.org: > reassign 1050429 gcc-13 13.2.0-2 Bug #1050429 [musl-tools] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Bug reassigned from package 'musl-tools' to 'gcc-13'. No longer marked as found in version

Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

reassign 1050429 gcc-13 13.2.0-2 notfound 1050429 12.3.0-8 affects 1050429 musl-tools thanks Dixi quod… >The -EL is not even musl-specific?! > >(sid_mips64el-dchroot)tg@eller:~$ cat >"/usr/lib/mips64el-linux-musl/musl-gcc.specs" […] Worse, doing mips64el-linux-gnuabi64-gcc{,-12} -dumpspecs and

Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

Dixi quod… >(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -EL >(sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -specs >"/usr/lib/mips64el-linux-musl/musl-gcc.specs" >mips64el-linux-gnuabi64-gcc: error: unrecognized command-line option '-EL' >(sid_mips64el-d

Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'

Dixi quod… >According to upstream documentation, -EL is supposed to be supported >by the compiler driver: OK so it’s not the compiler *driver*… (sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -EL (sid_mips64el-dchroot)tg@eller:~$ mips64el-linux-gnuabi64-gcc hi.c -specs "/usr/

  1   2   3   4   5   6   7   8   9   10   >