[MacPorts] #59080: dnscrypt-proxy: fatal error: unexpected signal during runtime execution

[MacPorts]

#59080: dnscrypt-proxy: fatal error: unexpected signal during runtime execution
-----------------------------+--------------------
  Reporter:  iEFdev          |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.5.4
Resolution:                  |   Keywords:
      Port:  dnscrypt-proxy  |
-----------------------------+--------------------

Comment (by ryandesign):

 Replying to [ticket:59080 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/59080#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS