I've started with a clean pkg dir. It's odd; the mtimes look correct (same inside/outside container). the "buildid" to the compile commands s the same on each run too.
Does anyone know if there's a way to print out the "StaleReason" that the code collects, that might help me find out what gate I'm failing. On Wednesday, December 7, 2016 at 11:08:14 PM UTC, andrey mirtchovski wrote: > > it's also possible that you need to do "go build -i" just in case your > dependencies are outdated. i had the same issue today with a windows > piece of code that rebuilt sqlite3 every time. > > > On Wed, Dec 7, 2016 at 2:57 PM, Dave Cheney <[email protected] > <javascript:>> wrote: > > Docker add, or whatever is pushing files into your container is probably > not respecting timestamps so the .a files are older with respect to .go > files (pkg sorts above src) > > > > Why do you want to build inside a container, is that just adding an > extra level of indirection to what is a simple process? > > > > -- > > You received this message because you are subscribed to the Google > Groups "golang-nuts" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
