cmd/link: -pluginpath seems to no longer work with go1.13 #34143
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
go build -ldflags "-pluginpath=custom/path" -buildmode=plugin ./path/to/plugin
With go1.13 this seems to no longer map the packages to the custom path.
What did you expect to see?
I have the variable Version in my main package
With go 1.12 after running the strings utility on the produced binary, I would see this somewhere in the output:
custom/path.Version
What did you see instead?
With go1.13 I now see this instead:
path/to/plugin.Version
Could this be related to go modules?
The text was updated successfully, but these errors were encountered: