-
Notifications
You must be signed in to change notification settings - Fork 154
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 native Android port #1118
Comments
How does native-comp work in this case, or is it also not supported? Straight also uses Emacs sub processes to byte-compile elisp files, so I don't think it'd be easy to support under those constraints. |
On this distribution of Emacs, does a form like |
It doesn't appear to support native-comp.
It does if I use the correct binary name and path. Emacs on Android is a little weird, though. If I evaluate |
Okay, so it sounds like we just need to adapt things to work in the environment. What's the error you see during bootstrap? |
Sorry for the long delay. This is what the debugger shows on startup:
|
We need to see the logs of the Emacs subprocess to debug. I've filed #1122 to improve the logging. Try editing the installation snippet in your init-file to refer to |
[#1118] More logs on failed bootstrap
Is this still a thing? I'm confused. Does straight not work on Android? |
No, I couldn't get it to work on Android. Since opening this I've moved back to package.el though, so I won't be of any help in fixing it. |
I got this error when trying to get straight for android. Any idea how to fix it?
|
straight.el
fails to bootstrap on the new native Android port of Emacs. Emacs has access togit
and other tools installed with Termux. I think the issue comes from trying to invoke Emacs from within Emacs, which is apparently never going to work reliably on Android (see the README from the SourceForge page I linked above).It's easy to reproduce even with a config that only contains the bootstrap snippet and this snippet to add Termux tools to the path:
The text was updated successfully, but these errors were encountered: