-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Git Submodule Checkout Instructions and Please Upload to Dybvig's/Cisco's Mainline Code #33
Comments
Thanks for the suggestion! I'm adding those There are a number of pending upstreaming PRs for the Meanwhile, this repo exists to make the Racket branch of Chez Scheme (which is developed day-to-day within the |
Closes racket#33 Original commit: racket/ChezScheme@c22f5a3
Closes racket#33 Original commit: racket/ChezScheme@261fc14
I have actually figured it out after asking on StackOverflow, but it would be useful to your users, particularly those that are not very Git savvy to give instructions regarding checking out the submodules (nanopass, zlib, etc.) before starting to
./configure
.Initially it repeatedly complained about the lack of the nanopass, zlib (etc.) submodules, when I
"./configured"
and it took me a while, as well as some help to figure it out.Also clearer instructions for making and installing Chez Scheme would be welcome. I realize that this is intended as the backend for future versions of Racket, however since your project now does support 64 bit aarch64 on ARM, while the mainline Dybvig/Cisco project still does not, I did resort to your version of Chez Scheme when trying to install Chez Scheme on a Raspberry Pi running aarch64 Raspberry Pi OS (formerly called Raspbian).
Uploading or backporting or offering a pull request for the appropriate code to the mainline Chez Scheme project, as well better documentation overall would be very welcome.
I did finally manage to install Chez Scheme on aarch64 on the Raspberry Pi, so for that and for your work on Racket, a big thank you!
The text was updated successfully, but these errors were encountered: