On Mon, Jun 1, 2020 at 3:17 am, Shengjing Zhu <z...@debian.org> wrote:
On Sun, May 31, 2020 at 9:51 PM Pirate Praveen
<prav...@onenetbeyond.org> wrote:
Package: gccgo-go
Version: 2:1.14~1~bpo10+1
Severity: important
X-debbugs-cc: debian-backpo...@lists.debian.org
Changing build dependency to golang-go (>= 2:1.14~) from golang-any
(>=
2:1.14~) works. I wonder why gccgo-go is selected over golang-go in
buster-backports though. It builds fine in sid when gccgo-go (>=
2:1.14~) is used as build dependency.
gccgo-go (>= 2:1.14) doesn't mean this version implements go1.14
features.
As in buster-backports, the gccgo-go points to gccgo-8, which
implements go1.10 features.
You can always check what version of go spec is implemented, by
running `go version`.
Its a bit misleading, but thanks for explaining. I thought it could be
the older gcc version, hence confirmed on sid with newer gcc version.
Can't gccgo-8 then provide gloang-any (=2:1.10)?
Command used to build the backport is,
sbuild -A -s --force-orig-source -c buster-amd64-sbuild
--extra-repository='deb http://deb.debian.org/debian
buster-backports
main' --extra-repository='deb
http://incoming.debian.org/debian-buildd
buildd-buster-backports main' --build-dep-resolver=aptitude
--no-run-lintian
github.com/cloudflare/tableflip
# github.com/cloudflare/tableflip
src/github.com/cloudflare/tableflip/fds.go:82:13: error: reference
to
undefined identifier ‘net.ListenConfig’
lc *net.ListenConfig
^
This is the go1.11 feature. See
https://github.com/golang/go/issues/9661
As gcc maintainers are unlikely to backport gcc, so there's nothing we
can do to make gccgo build this.
What can be fixed is why your build env picks up gccgo instead of
golang-go.
That will also work. I think if gccgo-8 did not Provide golang-any
2:1.14 (and instead provided only golang-any 2:1.10), aptitude
(build-dep resolver) would have picked golang-go correctly.
--
Shengjing Zhu
