gcc 5 is breaking the zarafa configure script and the compiled result.
=> You'll need to install gcc4 from Archlinux Rollback Maschine:
http://seblu.net/a/arm/2015/06/01/core/os/
=> Or build and install gcc4 with gcc5 for arm from repo
git clone https://github.com/archlinuxarm/PKGBUILDs.git
cd PKGBUILD
git checkout b1884b6d1950422a32f9ced0be6d5492e4315547
Search Criteria
Package Details: kopano-core 11.0.2-1
| Git Clone URL: | https://aur.archlinux.org/kopano-core.git (read-only, click to copy) |
|---|---|
| Package Base: | kopano-core |
| Description: | Foundation for groupware messaging enabling clients |
| Upstream URL: | https://www.kopano.com/ |
| Licenses: | AGPL3 |
| Groups: | kopano |
| Submitter: | martimcfly |
| Maintainer: | None |
| Last Packager: | martimcfly |
| Votes: | 6 |
| Popularity: | 0.000000 |
| First Submitted: | 2018-05-30 22:36 (UTC) |
| Last Updated: | 2022-03-31 19:38 (UTC) |
Dependencies (43)
- catdoc
- gawk (gawk-gitAUR, busybox-coreutilsAUR)
- libiconv
- libxslt (libxslt-gitAUR)
- mariadb (mysql55AUR, mysql56AUR, mytop-gitAUR, mysqlAUR, mysql81AUR, mysql57AUR, mysql80AUR, mariadb-lts, percona-server)
- poppler (poppler-gitAUR)
- python-bsddb
- python-dateutil
- python-magic (python-magic-gitAUR)
- python-pilkit
- python-pytz
- python-tzlocal
- python-xapian
- unzip (unzip-natspecAUR, unzip-zstdAUR)
- w3m
- binutils (make)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-c-aresAUR, curl-gitAUR) (make)
- gcc (gccrs-gitAUR, gcc11AUR, gcc-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- git (git-gitAUR) (make)
- Show 23 more dependencies...
Required by (4)
Sources (1)
martimcfly commented on 2015-07-01 14:20 (UTC)
jelly commented on 2015-04-29 19:37 (UTC)
Also notice that you will have to change your SSL settings https://community.zarafa.com/pg/blog/read/28319/zcp-7112-final
jelly commented on 2015-04-29 19:36 (UTC)
Just noticed the package was out of date. I've updated it to 7.1.12. I am not sure if people are interested in updating to 7.2.0 yet, but I have to package the new search and make it somehow work with the current python-{daemon,lockfile}.
rolek commented on 2014-12-18 08:33 (UTC)
We're running Zarafa on Slackware and we have the same problem. We've seen that the problem occurs a lot less often if we ensure no connections are made to the zarafa-server process before it is fully started. So, our Zarafa startup procedure now looks like:
- Stop postfix
- Disable access to the unix socket**
- With iptables, drop incoming traffic to ports 236 and 237
- Start zarafa-server
- Wait for 10 seconds
- Start the other zarafa daemons
- Allow incoming traffic to ports 236 and 237
- Allow access to the unix socket
- Start postfix
** On our system, the socket path is /var/run/zarafa/zarafa, so this is easily done by changing the access right on the /var/run/zarafa dir. On Arch, this might be different.
I hope this is useful to you.
jelly commented on 2014-11-03 19:03 (UTC)
Got the same problem here, not sure what the issue is. Looking into it with upstream :-)
martimcfly commented on 2014-10-29 17:54 (UTC)
On ARM 7.1.11 just exited right after start. That's why I didn't integrate it.
Pinned Comments