<john-mcaleely> I'm seeing reports, which I don't fully have to hand, that some go binaries are not running on current snappy rpi images. is this a known issue?
<ogra_> given that snapd is go itself, these must be very specific go bits that dont work in your binaries then
<john-mcaleely> hmm. the log message is: Oct 1 20:59:49 PiCloud snap[3346]: runtime: this CPU has no floating point hardware, so it cannot run
 Oct 1 20:59:49 PiCloud snap[3346]: this GOARM=6 binary. Recompile using GOARM=5.
 let me dig in to how that snap is produced
<ogra_> doea snap list work (or any other snap command)
<john-mcaleely> I assume the platform is Pi2, but that's one of the things I don't have exactly, yet
 yes
 so I take your point that something odd is up
<ogra_> pi2 or 3 shouldnt make any difference
<john-mcaleely> hmm
<jdstrand> john-mcaleely: that is probably the snap-confine bug stripping out auxv. that was fixed a while ago. you should use updated images
<ogra_> the image is the same, only the uboot binary differs
--> oparoz (~oparoz@46.166.137.241) has joined #snappy
<john-mcaleely> jdstrand, aha. Got a bug # so I can read?
<-- oparoz has quit (Client Quit)
<ogra_> LOL
<john-mcaleely> fwiw, the issue manifests after an update