Bug#948317: gcc-10: Please disable gm2 on ia64

On 7 Jan 2020, at 08:57, John Paul Adrian Glaubitz wrote: > On 1/7/20 9:54 AM, Matthias Klose wrote: >>> The gcc-10 build currently fails on ia64 when trying to build gm2 [1], >>> thus I have disabled gm2 for a local test build. >> >> how does it fail? > > The assembler is complaining [1]: >

Bug#922496: GCC 9: gnat ftbs on kfreebsd-*

Control: tags -1 patch upstream Control: forwarded -1 https://gcc.gnu.org/ml/gcc-patches/2019-07/msg00309.html On Sun, Feb 17, 2019 at 07:44:37AM +0100, Matthias Klose wrote: > Package: src:gcc-9 > Version: 9-20190216-2 > Tags: important > Severity: sid bullseye > > ftbfs, and we still have

Bug#929311: gcc-9: please include fix for pr87338

Control: tags -1 pending (sort of; changelog won't close this bug) On 21 May 2019, at 14:24, Jason Duerstock wrote: > > Package: gcc-9 > Version: 9-20190428-1 > Severity: normal > User: debian-i...@lists.debian.org > Usertags: ia64 > > Dear Maintainer, > > Please include the fix for pr87338

Bug#927976: gcc-8: FTBFS on ia64 due to bootstrap comparison failure

Source: gcc-8 Version: 8-20180308-1 Severity: important Tags: upstream patch Forwarded: https://gcc.gnu.org/ml/gcc-patches/2019-04/msg01000.html X-Debbugs-Cc: debian-i...@lists.debian.org Hi, A bug in a new GCC 8.1 feature was exposed by an updated binutils with debug_view support, which causes

Bug#897416: gcc: Decimal float support is not enabled on kfreebsd-amd64

c. Additionally, this patch use x86_64*- > > > > *- > > > > gnu* > > > > to also cover the future implementation of 64bit Hurd. > > > > > > this is not applied upstream. Please test the patch on trunk, > > > forward > > > it upstream and make sure it get

Bug#897416: mpfr4: FTBFS on kfreebsd-amd64

On 3 May 2018, at 09:21, Svante Signell <svante.sign...@gmail.com> wrote: > On Wed, 2018-05-02 at 12:51 +0100, James Clarke wrote: >> Control: reassign -1 gcc-7 >> Control: retitle -1 gcc: Decimal float support is not enabled on kfreebsd- >> amd64 >> >>

Bug#897416: mpfr4: FTBFS on kfreebsd-amd64

Control: reassign -1 gcc-7 Control: retitle -1 gcc: Decimal float support is not enabled on kfreebsd-amd64 On 2 May 2018, at 10:38, Svante Signell wrote: > > Source: mpfr4 > Version: 4.0.1-1 > Severity: important > Tags: patch > User: debian-...@lists.debian.org >

Bug#884642: libgo11: Please backport upstream sparc64 fix

Package: libgo11 Version: 7.2.0-17 Tags: upstream fixed-upstream patch User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@lists.debian.org Hi, For a while, libgo11 on sparc64 has been broken, with executables crashing with messages like: > runtime: lfstackpush

Bug#833829: libgcc-6-dev: Missing crtfastmath.o on kfreebsd-*

On Tue, Sep 06, 2016 at 03:17:52PM +0200, Andreas Beckmann wrote: > Control: retitle -1 libgcc-6-dev: Missing crtfastmath.o on kfreebsd-* > Control: affects -1 + src:vlc > > On Tue, 9 Aug 2016 11:39:54 +0200 Matthias Klose wrote: > > > I'm unable to build a package because

Bug#823937: gcc -E has __DATE__/__TIME__ as Jan 1 1970 00:00:00

On Tue, May 10, 2016 at 04:32:58PM +0100, James Clarke wrote: > Package: gcc-5 > Version: 5.3.1-17 > Severity: normal > Tags: upstream patch > Control: clone -1 -2 > Control: reassign -2 gcc-6 6.1.1-1 > > Hi, > With the SOURCE_DATE_EPOCH patch from upstream, the __D

Bug#854090: gcc-6: Please enable PIE hardening flags by default on sparc*

Package: gcc-6 User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@lists.debian.org Please enable PIE by default on sparc and sparc64. Regards, James

Bug#854061: Lack of hardening=+pie gives unwanted, unsilenceable noisy compiler output

Package: gcc-6, dpkg-dev Severity: important X-Debbugs-Cc: debian-ports-de...@lists.alioth.debian.org Control: block 851720 by -1 As far as I can tell, no progress has been made on this issue since the few discussions on debian-devel[0]. The current state is not desirable, and in fact is causing

Bug#851698: Dangling symlinks in /usr/share/man

Package: gcc Version: 4:6.2.1-1 Severity: important The following symlinks are currently dangling: /usr/share/man/man1/gcc-ar.1.gz -> gcc-ar-6.1.gz /usr/share/man/man1/gcc-nm.1.gz -> gcc-nm-6.1.gz /usr/share/man/man1/gcc-ranlib.1.gz -> gcc-ranlib-6.1.gz

Bug#850250: FTBFS on sparc with DEB_BUILD_OPTIONS=nolang=biarch

Source: gcc-6 Version: 6.3.0-2 Tags: patch User: debian-sp...@lists.debian.org Usertag: sparc X-Debbugs-Cc: helm...@debian.org, debian-sp...@lists.debian.org Thanks to the recent changes to get gcc to target ultrasparc by default, the biarch build is now successful. However, it still fails in

Bug#849542: PIE specs ignored even with DEB_BUILD_MAINT_OPTIONS hardening

Package: gcc-6 Version: 6.2.1-7 Severity: important The check introduced to ignore dpkg's PIE specs when PIE is not enabled by default is wrong, and ends up ignoring them even when hardening=+all or hardening=+pie is present in DEB_BUILD_MAINT_OPTIONS. The current check is: > if

Bug#840574: Please backport libgo fixes for sparc64

/changelog +++ gcc-6-6.2.0/debian/changelog @@ -1,3 +1,10 @@ +gcc-6 (6.2.0-9+sparc64) UNRELEASED; urgency=medium + + * Include go-relocation-test-gcc620-sparc64.obj.uue to fix libgo's +debug/elf TestDWARFRelocations test case. + + -- James Clarke <jrt...@jrtc27.com> Thu, 20 Oct 2016 20

Bug#840574: Please backport libgo fixes for sparc64

anything else to make this happen. I will also see if I can get them backported upstream (though even with that you'll still need to faff about with the .obj or drop the test...). Thanks, James > On 16.10.2016 19:40, James Clarke wrote: > > Control: tags -1 - help + patch > > &

Bug#840574: Please backport libgo fixes for sparc64

or gcc-6, but what about the clone changes? I can understand if that's too invasive, but backporting would be great. Regards, James > On 12.10.2016 23:35, James Clarke wrote: > > Source: gcc-6 > > Version: 6.2.0-6 > > User: debian-sp...@lists.debian.org > >

Bug#840574: Please backport libgo fixes for sparc64

Source: gcc-6 Version: 6.2.0-6 User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@lists.debian.org Tags: patch fixed-upstream Hi, Could you please backport the patches listed below so that we can have a working gccgo? They fix the (minor) issue of using the wrong

Bug#823937: gcc -E has __DATE__/__TIME__ as Jan 1 1970 00:00:00

Package: gcc-5 Version: 5.3.1-17 Severity: normal Tags: upstream patch Control: clone -1 -2 Control: reassign -2 gcc-6 6.1.1-1 Hi, With the SOURCE_DATE_EPOCH patch from upstream, the __DATE__ and __TIME__ macros always give Jan 1 1970 00:00:00 when running the preprocessor on its own with gcc