I just landed into seafile, and found out that you have a wonderful RPi server! Thanks for that!
On the other side, my RPi is busy with some video content, so I wanted to try the server on my Pine64, which is arm64 (aarch64) linux powered… But, it failed miserably.
It’s something I can do to help development on the aarch architecture? I’d be happy to use one of my boxes to compile seafile in aarch64…
Now, the workaround/how-to to make it work on a aarch64, but I warn you: It’s very ugly.
> Generating ccnet configuration in /home/seafile/ccnet...
> ./setup-seafile.sh: line 483: /home/seafile/seafile-server-6.0.6/seafile/bin/ccnet-init: No such file or directory
and doing a fast “file”, it looks for the ld.linux.armhf, which I don’t have on my box…
> seafile@pine64:~/seafile-server-6.0.6$ file /home/seafile/seafile-server-6.0.6/seafile/bin/ccnet-init
> /home/seafile/seafile-server-6.0.6/seafile/bin/ccnet-init: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.26, BuildID[sha1]=3202b5db82317ff70cbfc50e050c436d8919f72c, stripped
The thing is, it doesn’t find it because is libc6-aarch64, not libc6-armhf (Although aarch64 is still architecture compatible). So… installing cross libraries and some armhf libs by hand, ccnet-init executed and the installer resulted ok:
created symlink to the ld.linux-armhf.so.3 and also libselinux1 on a common place and updated LD_LIBRARY_PATH:
And voilá, setup finished, seafile started and seahub working also.
> seafile@pine64:~/seafile-server-6.0.6$ LD_LIBRARY_PATH=/usr/arm-linux-gnueabihf/lib/:/home/seafile/lib/arm-linux-gnueabihf/ ./seafile.sh start
> [12/07/16 16:44:52] ../common/session.c(132): using config file /home/seafile/conf/ccnet.conf
> Starting seafile server, please wait ...
> Seafile server started
Please contact me if willing to compile on aarch64 and need anything…