-
Notifications
You must be signed in to change notification settings - Fork 17.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: support shared objects (-buildmode=shared
) for more than just linux/amd64
#12346
Comments
FWIW, I have implementations for arm and arm64 done and am working on getting them cleaned up for submission soon. I have done some work on ppc64le and have come to the conclusion that it's going to be a bit of a pain. I keep avoiding thinking about 386 -- fancy helping out on that? :-) |
Where are your working branches for arm, etc? |
yeah. not a trivial change set. On Wed, Aug 26, 2015 at 6:27 PM, Michael Hudson-Doyle <
|
No. I'll have a better organized set of changes for arm64 only up today I hope. |
This can be closed now :-) |
Well, unless someone is planning on working on ppc64(be) or mips or non-linux (I'm certainly not) |
right on. I'm hoping some release notes will break down the availability better for folks. |
This issue is a tracker for supporting additional GOOS/GOARCH shared objects than just
linux/amd64
.While packaging go1.5 for fedora, which has the goal/requirement of shared objects. This is a security and update-ability requirement and not something I intend to partially deploy for general consumption.
Initially this target would be linux/386 and linux/arm, though arm64, etc would follow I'm sure.
https://bugzilla.redhat.com/show_bug.cgi?id=1256525 is the tracker for adding shared objects to the fedora golang rpms.
/cc @mwhudson @ianlancetaylor
The text was updated successfully, but these errors were encountered: