New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for ARM? #10
Comments
Hi, @saimon-moore. Sorry for the inconvenience. |
Yes I will wait patiently. Unfortunately I don't have the chops to try it myself :( Thank you very much |
Hey 👋 I haven't run any C code since college, so my knowledge is pretty much gone, but if someone can give me some guidance I can help try to build this on Apple silicon. (getting the segmentation fault myself too) |
Hi, saimon-moore and norim13. Sorry for my late reply. |
Just tried both, but unfortunately I think none worked 😕 It crashes immediately once I select the folder I want to open. Is there any way for me to give you better data about the actual error? Any logs I can fetch somewhere? (btw, apologies for taking so long... only saw this now 🤦) |
Hmm, the cause of the crash should be isolated first.
In fact, it would be great if someone could debug it on mac... |
Since this issue hasn't been closed, I assume you would still need someone to test on Apple Silicon? I have a m1 max macbook and is glad to help. |
Also, have you considered releasing two versions (two .tar.xz files or two .apps in one .tar.xz file in this case), one for each architecture? Personally I generally dislike Universal Binaries because it wastes space while adding no real benefit to me, and it seems to complicate the build process sometimes, I heard. It seems like both sides have a valid argument, and I've seen big companies taking different approaches. |
Hi,
I just tried this on an M1 and it crashes with a segfault just as soon as I try to open a folder exported with https://github.com/rusq/slackdump/blob/master/doc/usage-export.rst#export-types (standard export)
Any chance, a build for arm will become available soon?
The text was updated successfully, but these errors were encountered: