execution errors in MacOS

I have successfully been able to build and run vector-ble in linux arm (arm64, on manjaro, pine book pro).
I have been able to build vector-ble on both M1(arm64) and Intel(x64) Macs. However note the following:

1. During compilation 'pkg-config' had to be installed (in addition to Go). I compiled it from source.
2. In both the arm64 and x64 versions of macOS, I received the following alternating errors messages when running:
`
michael@MoonMini vector-bluetooth % ./vector-ble
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x10255a910]`
`
goroutine 19 [running]:
github.com/currantlabs/ble/linux/hci.(*HCI).sktLoop(0x14000106780)
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/hci/hci.go:267 +0x80
created by github.com/currantlabs/ble/linux/hci.(*HCI).Init
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/hci/hci.go:146 +0x4f4
`
and
`
michael@MoonMBP vector-bluetooth % ./vector-ble
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x11bc802]
`
`
goroutine 1 [running]:
github.com/currantlabs/ble/linux/hci.(*HCI).send(0xc000001c80, 0x12c0bc0, 0x14503e8, 0xc000068778, 0xc000176240, 0xc000105bd8, 0x10, 0x12354c0)
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/hci/hci.go:249 +0x302
github.com/currantlabs/ble/linux/hci.(*HCI).Send(0xc000001c80, 0x12c0bc0, 0x14503e8, 0x0, 0x0, 0xc00001c240, 0x0)
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/hci/hci.go:221 +0x45
github.com/currantlabs/ble/linux/hci.(*HCI).init(0xc000001c80, 0x1286658, 0xc000001c80)
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/hci/hci.go:178 +0x52
github.com/currantlabs/ble/linux/hci.(*HCI).Init(0xc000001c80, 0x0, 0x0)
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/hci/hci.go:147 +0x596
github.com/currantlabs/ble/linux.NewDevice(0x1256b60, 0xc000176180, 0x20)
/Users/michael/go/pkg/mod/github.com/currantlabs/ble@v0.0.0-20171229162446-c1d21c164cf8/linux/device.go:21 +0x5f
github.com/digital-dream-labs/vector-bluetooth/ble/conn.New(0xc0000686c0, 0x5, 0xc0000686c0, 0xc000013190)
/Users/michael/Downloads/vector-bluetooth/ble/conn/conn.go:41 +0x1fa
github.com/digital-dream-labs/vector-bluetooth/ble.New(0xc000105ea8, 0x2, 0x2, 0x126c8a0, 0x100000000000178, 0x2a09218)
/Users/michael/Downloads/vector-bluetooth/ble/vector.go:57 +0xb1
github.com/digital-dream-labs/vector-bluetooth/cli.BLEShell()
/Users/michael/Downloads/vector-bluetooth/cli/blecli.go:21 +0xd4
main.main()
/Users/michael/Downloads/vector-bluetooth/cmd/main.go:6 +0x25
`

Regards,
-Michael

Start by reproducing the panic on the reported M1 and Intel macOS systems, then trace the stack from cmd/main.go through cli/blecli.go, ble/vector.go, and ble/conn/conn.go into the github.com/currantlabs/ble/linux/hci calls. Done means vector-ble starts without either nil-pointer panic on the reported macOS architectures.

Written by the indexing model from the issue text.