I fixed this problem a while ago upstream for Go 1.7 ( https://github.com/golang/go/issues/15443, https://github.com/golang/go/issues/15887). The question is, do we backport the fixes for golang-1.6, or just remove it from the archive? I'd lean towards the latter.
On 1 November 2016 at 08:18, Niels Thykier <ni...@thykier.net> wrote: > On Mon, 12 Sep 2016 00:55:37 +0200 Balint Reczey > <bal...@balintreczey.hu> wrote: > > Source: golang-1.6 > > Version: 1.6.3-1 > > Severity: important > > User: bal...@balintreczey.hu > > Usertags: pie-bindnow-20160906 > > Justification: FTBFS on amd64 with extra hardening > > Tags: patch > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build on > > amd64 with patched GCC and dpkg. > > > > The rebuild tested if packages are ready for a transition > > enabling PIE and bindnow for amd64. > > > > For more information about the changes to sid's dpkg and GCC please > > visit: > > https://wiki.debian.org/Hardening/PIEByDefaultTransition > > > > Relevant part (hopefully): > > ... > > [...] > > Dear maintainers, > > The thread-sanitizer (used by golang) is not compatible with PIE[1]. > > * Please disable either PIE or the thread-sanitizer. > * From a quick look, it appears that the thread-sanitizer is done by > upstream. > * On that basis, I think we should prefer that over PIE in the given > case (for consistency with upstream). > > > Thanks, > ~Niels > > [1] https://wiki.ubuntu.com/SecurityTeam/PIE > > _______________________________________________ > pkg-golang-devel mailing list > pkg-golang-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-golang-devel >
