/rclone version
./rclone: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./rclone)
./rclone: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./rclone)
the synbox uses AMD64, same as WSL
uname -a
Linux bnas 4.4.180+ #42661 SMP Mon Jun 27 15:05:48 CST 2022 x86_64 GNU/Linux synology_apollolake_218+
```
this is the output of rclone version, running on WSL
```
rclone v1.62.2-DEV
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.90.1-microsoft-standard-WSL2 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.20.2
- go/linking: dynamic
- go/tags: cmount
```
and is the official rclone running on synology
```
rclone version
rclone v1.62.2
- os/version: unknown
- os/kernel: 4.4.180+ (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.20.2
- go/linking: static
- go/tags: none
```
so now i compiled on synbox, go build -tags cmount, did not look correct
i re-ran the compile and same result, the go/tag is not set
user99@bnas:~/rclone/go/rclone-1.62.2$ go build -tags cmount
user99@bnas:~/rclone/go/rclone-1.62.2$ ./rclone version
rclone v1.62.2-DEV
- os/version: unknown
- os/kernel: 4.4.180+ (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.20.2
- go/linking: static
- go/tags: none
user99@bnas:~/rclone/go/rclone-1.62.2$ ./rclone mount wasabi01: ~/rclone/mount/remote
2023/03/20 11:52:59 Fatal error: failed to mount FUSE fs: fusermount: exec: "fusermount3": executable file not found in $PATH
user99@bnas:~/rclone/go/rclone-1.62.2$ ./rclone cmount wasabi01: ~/rclone/mount/remote
Error: unknown command "cmount" for "rclone"
Did you mean this?
mount
Run 'rclone --help' for usage.
You could use 'rclone selfupdate' to get latest features.
2023/03/20 11:53:05 Fatal error: unknown command "cmount" for "rclone"
Did you mean this?
mount
the issue with no support for fuse3 on a linux machine is going to an issue in the forum, well, it already is an issue.
so if/when i can get this to work on the synbox, i will create a how-to guide.
when i compiled it the first time, it seems to work, no errors.
when i ran the command, there was no output, so i believe there are no issues.