-
Notifications
You must be signed in to change notification settings - Fork 6
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
Make install_buck and Make debug Error #2
Comments
Would you be so kind as to take a look at this? @Angel-Cortez |
Fixed, would you give me permission to push up a branch? @Angel-Cortez |
Create a PR with the fix, and we'll get this sorted |
@Angel-Cortez so it wasn't as simple as I thought. Part of this was actually modifying the RIBs dependency files that were downloaded, part of this was building a fork of buck, part of this was the order of commands and modifying the make file to work with M1 machines. For RIBs itself, I had to:
Then, I had a lot of issues making project. I found a fork of buck that supports M1 with java 11.0.16-librc https://github.com/traveloka/buck , I built that using:
Then I modified the make file to use that newly generated buck.pex I pasted into tools/buck.pex and use flags --config java.target_level=11 --config java.source_level=11 when using buck. To make the project, first I run make build then make project. If I do make project first, I get an architecture error. But if I run make build first, then it's okay. I can still push what I have up, but maybe I'd need to make a fork of RIBs as well with these fixes. |
Trying to get the example to run
My machine:
Model Name: Mac Studio
Model Identifier: Mac13,1
Chip: Apple M1 Max
Total Number of Cores: 10 (8 performance and 2 efficiency)
Memory: 32 GB
make install_buck currently doesn't work, the pex file doesn't exist at the current location. I updated install_buck to this instead:
This installs buck correctly. Before I push up the fix, I want to make sure my make debug works as well.
Running make debug in the root of the project gives the following error
The text was updated successfully, but these errors were encountered: