Hi Tianon, all, > On Sun, Jun 01, 2014 at 01:33:04AM +0100, Michael Tautschnig wrote: > > Now I must admit that I'm pretty much at loss with the build system here - > > most > > likely this is an upstream issue, but I'm not sure whether the build scripts > > (with their bold warning) have any influence here. > > For how we use them, the build scripts are essentially just a wrapper > around "go build", especially to ensure that the "dockerinit" binary is > compiled statically. Are you doing anything like forcing gccgo or > something like that to perform this analysis? >
For the record, I'm replacing gcc by a wrapper script that will invoke both original gcc as well as our own compiler, which then provides those further warnings/errors. [...] > > then it will have to make a decision on which section to put that symbol > > into - > > is it data or code? If the declaration from _cgo_main.c happens to be > > ignored, > > you're lucky - else things will crash badly at runtime. > > > > Unfortunately I'm clueless on how either of the two files were generated - > > even > > go build -x -work did not seem to print a command that (in some obvious way) > > generated the _cgo_main.c file. (I'm happy to perform further > > investigations if > > any guidance could be provided.) > > I've got to admit that I myself am also at a loss here. This looks > pretty hairy, but we (upstream or downstream in Debian) haven't seen any > reports of any kind of crashes related to this, so either we're > extremely lucky, or Go's compiler is doing other magic behind the scenes > that it's not sharing when you ask it to dump things (which, from the > disdain the upstream Go developers have for "C problems", doesn't seem > at all unlikely). > > TL;DR, I'm as much at a loss as you are and would love further guidance > on how to proceed with this (or whether to do anything concrete as a > result of it). > So maybe a reasonable course of action is to leave things as they are, and just wait for further upstream releases? Those might well include fixes, even if not explicitly listing that problem. Feel free to ping me if such new releases become available, in which case I will be happy to give that package (version) another try. Best, Michael
pgp1CwNJJtLmD.pgp
Description: PGP signature
