autotrace-0.40.0-20200219-MacOS gives Illegal instruction: 4 on MacOS <10.13 · Issue #42 · autotrace/autotrace · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the issue title says, your autotrace-0.40.0-20200219-MacOS binary doesn't run on older MacOS systems (tested with El Capitan aka MacOS 10.11.6) and will give an "Illegal instruction: 4"! - On a MacOS Mojave (10.14.6) it will work and run instead. As far as I've seen this might be related to the used High Sierra SDK 10.13 to compile the whole.
Another point when building/recompiling your sources is that GraphicsMagick usage, which usually isn't needed at all here when using instead ImageMagick 6 (see: https://github.com/ImageMagick/ImageMagick6), which BTW includes "magick/api.h" and everything other relevant for building autotrace.
When using and linking against ImageMagick 6 autotrace works flawlessly under El Capitan here too.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
As the issue title says, your autotrace-0.40.0-20200219-MacOS binary doesn't run on older MacOS systems (tested with El Capitan aka MacOS 10.11.6) and will give an "Illegal instruction: 4"! - On a MacOS Mojave (10.14.6) it will work and run instead. As far as I've seen this might be related to the used High Sierra SDK 10.13 to compile the whole.
Another point when building/recompiling your sources is that GraphicsMagick usage, which usually isn't needed at all here when using instead ImageMagick 6 (see: https://github.com/ImageMagick/ImageMagick6), which BTW includes "magick/api.h" and everything other relevant for building autotrace.
When using and linking against ImageMagick 6 autotrace works flawlessly under El Capitan here too.
The text was updated successfully, but these errors were encountered: