Control: reassign 982701 src:golang-1.15 1.15.8-3 Control: reassign 982714 src:golang-1.15 1.15.8-3 Control: reassign 982724 src:golang-1.15 1.15.8-3 Control: reassign 982734 src:golang-1.15 1.15.8-3 Control: affects 982701 src:golang-github-pkg-profile Control: affects 982714 src:golang-github-jacobsa-ogletest Control: affects 982724 src:panicparse Control: affects 982734 src:delve
Hi Michael Hudson-Doyle, On Sat, Feb 13, 2021 at 06:03:25PM +0100, Lucas Nussbaum wrote: > Relevant part (hopefully): > > === RUN TestDebugger_LaunchInvalidFormat > > # github.com/go-delve/delve/_fixtures/buildtest > > loadinternal: cannot find runtime/cgo > > /usr/lib/go-1.15/pkg/tool/linux_amd64/link: running gcc failed: exit status > > 1 > > gcc: error: unrecognized command-line option ‘-mconsole’ > > > > debugger_test.go:58: go build error exit status 2 These failures(#982701,#982714,#982724,#982734) are related to the patch in golang-1.15/1.15.8-3 https://salsa.debian.org/go-team/compiler/golang/-/blob/debian/1.15.8-3/debian/patches/0007-cmd-link-check-CGO_CFLAGS-for-non-g-I-O-options-befo.patch I don't think such patch should be applied in bullseye. The investigation of LTO should be done it experimental first. Unstable and testing should focus on next stable release, which is bullseye currently. Can we revert this?
