On Mon, Sep 21, 2020 at 5:28 PM Matthias Klose <d...@debian.org> wrote: > > Control: severity -1 wishlist > > On 9/19/20 7:29 PM, Shengjing Zhu wrote: > > Source: gcc-10 > > Severity: important > > > > These files are missing in libgo-10-dev package: > > https://github.com/golang/gofrontend/tree/master/libgo/go/golang.org/x > > > > This causes containerd FTBFS on ppc64, > > https://buildd.debian.org/status/fetch.php?pkg=containerd&arch=ppc64&ver=1.4.1%7Eds1-1&stamp=1600269780&raw=0 > > > > go build golang.org/x/net/http2/hpack: no Go files in > > /usr/src/golang.org/x/net/http2/hpack > > go build golang.org/x/net/http/httpguts: no Go files in > > /usr/src/golang.org/x/net/http/httpguts > > go build golang.org/x/net/idna: no Go files in /usr/src/golang.org/x/net > > > > These files are in upstream libgo repo, and > > https://github.com/golang/gofrontend/blob/master/libgo/libgo-packages.txt > > GCC 10 is based on go 1.14.x. 1.15 (and likely 1.16) will be part of GCC 11.
This is not about go1.14 or go1.15. It's actually an upstream bug which I have forwarded later. https://github.com/golang/go/issues/41499 Let's see if upstream can fix this and then backport to gcc10. IIUC, bullseye will use gcc10? -- Shengjing Zhu