Skip to content
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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

madscientist159
Copy link

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.

@CLAassistant
Copy link

CLAassistant commented Nov 11, 2019

CLA assistant check
All committers have signed the CLA.

@madscientist159
Copy link
Author

madscientist159 commented Nov 12, 2019

Note that in order to build on POWER, you do need to point zm-build at the fixed junixsocket source tree here:
https://github.com/madscientist159/junixsocket/tree/junixsocket-parent-2.0.4-ppc64le

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.
Copy link
Contributor

@Prashantsurana Prashantsurana left a 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.

@madscientist159
Copy link
Author

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...

@gerrith3
Copy link

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.

@madscientist159
Copy link
Author

madscientist159 commented Apr 24, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants