tokeL
(toke lahti)
May 8, 2022, 2:24pm
1
Hi,
There are a few reports that newer Syncthing versions do not work with 10.11.
opened 02:21PM - 02 Mar 21 UTC
closed 10:04AM - 06 Mar 21 UTC
I'm using syncthing-macos 1.6.1-1 on Mac OS X (El Capitan, 10.11.6). Today, Sync… thing updated itself to version 1.14.0. Now the syncthing binary crashes on startup:
```
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
Referenced from: /Users/schuetzm/Library/Application Support/Syncthing-macOS/./syncthing
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: _clock_gettime
Referenced from: /Users/schuetzm/Library/Application Support/Syncthing-macOS/./syncthing
Expected in: /usr/lib/libSystem.B.dylib
```
It seems this is caused by building syncthing on a newer MacOS and not setting `MACOSX_DEPLOYMENT_TARGET`. See https://bugs.erlang.org/browse/ERL-256 for details.
So... is this even the right place to submit the bug? I.e., are you building your own syncthing binaries, or should I report it upstream?
Also they don’t with me.
Support for elCapitan was dropped with 1.13.1.
I’m not asking to get support for later versions.
What would be nice, would be a version of 1.13 that has automatic updating automatically off.
Or instructions on how to do that.
calmh
(Jakob Borg)
May 8, 2022, 3:37pm
2
You can set STNOUPGRADE=1
in the environment to prevent upgrades regardless of config. I think this is the most secure way to prevent an undesired surprise upgrade. If you use our LaunchD plist file, open it in an editor and add
<key>STNOUPGRADE</key>
<string>1</string>
to the environment section. Something like this:
...
<key>EnvironmentVariables</key>
<dict>
<key>HOME</key>
<string>/Users/USERNAME</string>
<key>STNORESTART</key>
<string>1</string>
<key>STNOUPGRADE</key>
<string>1</string>
</dict>
...
Then log out, log in (or launchd unload
the service follow by load).
system
(system)
Closed
June 7, 2022, 3:38pm
3
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.