Bug#904289: libgo build failure with GCC trunk 20181004

On Mon, Oct 8, 2018 at 8:59 PM, Matthias Klose wrote: > On 08.10.2018 11:47, Svante Signell wrote: >> On Fri, 2018-10-05 at 21:10 +0200, Svante Signell wrote: >>> On Fri, 2018-10-05 at 01:38 +0200, Matthias Klose wrote: Hi Svante, please have a look at the recent libgo build

Bug#876639: libgo11: Please consider backport "libgo: use gc's arch names as the default GOARCHs on MIPS"

Matthias Klose writes: > On 24.09.2017 11:36, Shengjing Zhu wrote: >> Package: libgo11 >> Version: 7.2.0-5 >> Severity: wishlist >> Tags: upstream >> X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org >> >> Dear Maintainer, >> >> Currently the pkg-go team uses gccgo to

Bug#683782: gccgo: please Recommend: binutils-gold on x86

On Tue, Aug 7, 2012 at 3:44 AM, Matthias Klose d...@debian.org wrote: On 04.08.2012 00:07, shawn wrote: Source: gcc-4.7 Version: 4.7.1-6 Severity: normal gccgo requires binutils-gold in order to fully use gcc's split stack feature. As this feature is heavily used by the core language

Bug#632003: Finding dlltool using gcc

Stephen Kitt st...@sk2.org writes: Is there a recommended approach to use to find dlltool using only i686-w64-mingw32-gcc? I don't know of one. I don't know why avoiding autoconf is desirable. However, if I were forced to do so, I would probably use gcc -v to get the target name and look for

Bug#628622: gccgo-4.6: Is gccgo GNU?

Some more information: the code described at http://golang.org/ is not gccgo. gccgo is a different compiler for the Go language, written as a frontend for gcc. gccgo is mentioned on gcc's home page, http://gcc.gnu.org/. It's another GCC frontend, just like the C, C++, Fortran, Java, Objective