Beego: 升级 macos 10.12.4 后 beego 跑不起来了

Created on 29 Mar 2017 · 7Comments · Source: astaxie/beego

Please answer these questions before submitting your issue. Thanks!

What version of Go and beego are you using (bee version)?
Go 1.8
beego 1.8
What operating system and processor architecture are you using (go env)?

GOHOSTARCH="amd64"
GOHOSTOS="darwin"

What did you do?

升级 macos 10.12.4

What did you expect to see?

正常运行

What did you see instead?

升级 macos 10.12.4 后 beego 跑不起来了

bee run

2017/03/28 17:06:08 SUCCESS  ▶ 0009 Built Successfully!
2017/03/28 17:06:08 INFO     ▶ 0010 Restarting 'medsearch'...
2017/03/28 17:06:08 SUCCESS  ▶ 0011 './medsearch' is running...

一直是 running，到不了打开端口那块

Source

uuappli

Most helpful comment

go build -ldflags -s

kayon on 30 Mar 2017

👍2 🎉1

All 7 comments

有设置安全策略吗？看下设置里的安全与防火墙

zjjott on 29 Mar 2017

https://github.com/golang/go/issues/19734

fuxiaohei on 29 Mar 2017

👍2

幸好没升级

joostshao on 30 Mar 2017

是一个Mac的BUG

linkerlin on 30 Mar 2017

go build -ldflags -s

kayon on 30 Mar 2017

👍2 🎉1

如果不适用gdb debug 可以临时 ln -s /usr/bin/true /usr/local/bin/dsymutil 解决

songcy6202 on 30 Mar 2017

If you build with -ldflags -s, which drops the DWARF information from the executable, then codesign produces a valid binary. I think this is mostly not Go's fault (except that Go works hard to put DWARF info in the binaries, unlike most OS X programs). Certainly for Go 1.5 but possibly long term we can suggest that people who need codesign can use -ldflags -s.