Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
plugin: plugin.Open() segfault with statically linked binaries #21822
What version of Go are you using (
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
What did you do?
What did you expect to see?
What did you see instead?
go run -ldflags '-extldflags "-static"' main.go
goroutine 1 [syscall, locked to thread]:
As Ian says, difficult and low priority. Unless an intrepid sort with the need and tenacity shows up to implement this, it won't happen.
I suppose we could produce a link-time error easily enough if both the
Building binaries dynamically fixes: - PKCS11 integration issues - FAB-6161 - It also enables the use of Go plugins in FAB-6159 This is required because Go plugins are not compatible with statically linked binaries (see golang/go#21822 ) NOTE: Using the dynamic build flag requires a custom image. Currently, hyperledger/fabric-baseos image does not include the C libraries required by the peer and orderer for dynamic linking Change-Id: Ifddcc563e3bca9e473e6e81f4c10c84da1a6cf6f Signed-off-by: Divyank Katira <Divyank.Katira@securekey.com>