-
Notifications
You must be signed in to change notification settings - Fork 87
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
Enable build on OpenPOWER systems (ppc64le) #156
base: develop
Are you sure you want to change the base?
Conversation
Note that in order to build on POWER, you do need to point zm-build at the fixed junixsocket source tree here: That appears to be the only other modification required, but I don't expect Synacor will want to redirect that repo. For now, it's fairly easy to just redirect the junixsocket repo to build (this is the only action that POWER users will need to take after download once this pull request is merged). This was tested with a full build of Zimbra 8.8.15 on a POWER9 / Talos II server. Zimbra is known to be functional since at least version 8.7 on POWER servers, and is currently being used in production on those servers at Raptor. |
Fix overly simplistic architecture check. We have been using Zimbra on POWER in production for around one year with this modification. Zimbra has been fast and reliable on these platforms.
3a84244
to
599942f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the submission. The changes looks good to me.
However from Zimbra product point of view, we are not certifying/supporting the non-x86 environment. hence I will not merge the changes to develop.
Why can't we get the changes in place for unofficial / non-certified systems? We can attest to the fact that Zimbra works very well on POWER systems since we use them in production with our own builds... |
So, I'm confused - Is Zimbra open source? And doesn't it embrace users that use open source, wherever and however they might use them? It seems like merging changes to enable additional features is typical in open source communities, even if they aren't supported by the corporate release, is typical. Is there some reason why you aren't taking additional features? Is the source base just for the corporately released/supported version? This is not typical in the open source communities that we usually work with. |
Just wanted to revisit this and ask if we could get the decision not to merge revisited? POWER is seeing a wider deployment especially in this age of cyberattacks, and it is probably not a great idea to force use of the known-insecure Intel ME or AMD PSP to use Zimbra. |
Fix overly simplistic architecture check.
We have been using Zimbra on POWER in production for around one year with this modification. Zimbra has been fast and reliable on these platforms.