dnscrypt-proxy: fatal error: unexpected signal during runtime execution

[iefdev (Eric F)]

dnscrypt-proxy fails to build…

:info:build fatal error: unexpected signal during runtime execution
:info:build [signal SIGSEGV: segmentation violation code=0x1 addr=0xb01dfacedebac1e pc=0x56f5fdf]

---

I'm on 10.7.5, with go @1.12.9_0 (active).

On older systems we get a message to add (when installing go):

export GO_EXTLINK_ENABLED="1"
export GO_LDFLAGS="\"-extldflags=-L/opt/local/lib -Wl,-headerpad_max_install_names -lMacportsLegacySupport\""

Don't know, but it doesn't show in the log, it only says: … && go build -ldflags="-s -w.

Tried with and without a default compiler. I haven't upgraded to 2.6.0 yet. Saw it was recommended to stay put a few days for <= 10.8.

---

btw: There's a new version out, and it also seems like the repo has moved from jedisct1->DNSCrypt (that version failed to when I tried).

Here's for 2.0.27:

github.setup        DNSCrypt dnscrypt-proxy 2.0.27

checksums           rmd160  8289cb74b8e0cfd2cb0da11ac32204c6022308e9 \
                    sha256  f1c28d86f5f98dd92f399d0b09c6ce639f8bd41c66edaea4d6785dfed489a6b1 \
                    size    2479482

[ryandesign (Ryan Carsten Schmidt)]

Replying to iEFdev:

Don't know, but it doesn't show in the log, it only says: … && go build -ldflags="-s -w.

The Portfile does set those ldflags explicitly. It is recommended in the dnscrypt-proxy build instructions. But those instructions are not aware that in MacPorts we actually want to set other flags.

I had hoped that switching the portfile to use the golang 1.0 portgroup might help automatically set the MacPorts flags. However, after looking at, it does not appear that that is the case; that seems like a bug in the portgroup to me. Also, I tried for a little while, but I was unable to understand how to make this port use the portgroup; perhaps someone more familiar with go can do that.

Tried with and without a default compiler. I haven't upgraded to 2.6.0 yet. Saw it was recommended to stay put a few days for <= 10.8.

Everything that could be rebuily with libc++ on 10.6-10.8 has been, so it's fine to upgrade now. If you encounter build failures with other ports, please file bug reports as usual.

btw: There's a new version out, and it also seems like the repo has moved from jedisct1->DNSCrypt (that version failed to when I tried).

I updated the port; see #59748.

[mf2k (Frank Schima)]

"The Portfile was updated, so that part was done. I still use an older legacy-version from their site instead. I think the problem is with 'go', and thats not fixed for Lion yet, I belive. I'll try it later. The one I have works, though I have to do a manual upgrade to the dns-vendors list, ocassionally. You can close this one."