-
Notifications
You must be signed in to change notification settings - Fork 357
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
Error building NyuziProcessor (probably NyuziToolchain) #193
Comments
This doesn't look familiar. I will do a clean install on my setup to try to reproduce it. |
Thanks for responding quickly. That'd be great. I'm not sure if I am missing any dependencies or is it related to permissions because the error msg didn't seem to say anything. I'll wait your response. Thanks. |
Unfortunately, I was not able to reproduce on my setup:
Configuration:
Yeah, that error message is not very helpful. :) I assume it is coming from ninja, but it's unclear. I will do a little more research to figure out where it is originating from. Could you please try the following?
|
So I remove the directory and tried running My Configuraion:
Output of
Does this give any idea? I also have a log file for the build. I could you that directly if that helps. |
I think the full log would be helpful (maybe create a gist and add a link to it). Thanks! |
Here's the link to the gist. It's quite long (that's expected) but I think that the last 50 lines would be of relevance to you. https://gist.github.com/gauravjain14/10691e9abf6cde6bc12978ce7000d140 Thanks |
One more thing, can you try from the tools/NyuziToolchain/build directory?
|
Sorry, should be:
|
Hi Jeff, Then on both the machines I cd'd into
and on both the machines I get the same error
Both are Ubuntu 16.04, with Python 3.7+ |
Thank you, that is really helpful. I will try upgrading my software, as it appears to be specific to newer versions of the tools. It looks like it's actually crashing ninja. A workaround you could try is using make instead of ninja. Here is a modified version of setup.sh: https://gist.github.com/jbush001/a0fbe1e5f5eb8068a4667439af728a53 |
Thanks for sharing the gist. After using make, I was able to pass through the
This seems to be related to verilator, but when I wrote a testbench to verify my installation of verilator that seemed to work fine. |
Sorry this is having so many problems. I haven't seen this before either. Can you double check the version with this command?
|
Thanks for actively responding.
On other lines - is there a docker image for Nyuzi? |
It appears you have a newer version of Verilator than is checked in (That is 4.012). Perhaps that is being installed by the package manager. It appears something broke with the latest version. I will need to debug that. I believe this could be fixed by uninstalling the system version and re-installing the version from the tree. However, there is a docker package for this that contains Verilator and the compiler (it's used during CI testing), which would probably save some trouble. It is here: https://hub.docker.com/r/jeffbush001/nyuzi-build. Let me know if you have any problems with it. |
Thanks for the pointers. When I let setup_tools.sh install verilator, it installs the version 4.03 (which I mentioned above). So I installed 4.012 from the verilator repository and then tried doing Thanks a lot for helping through this process. I can now go ahead and close the issue? |
Switch to make for building NyuziToolchain. It appears the latest version of ninja may not be working correctly with the build system. This may slow down the build a bit.
I've put in a workaround for the build issue, and I will open new issues to investigate the problems that were found here. Thank you for your help debugging this! |
Hi All,
I am trying to build on Ubuntu 16.04 with Python 3.7 and when I run the command
./scripts/setup,sh
, I get the following error after it asks forsudo
password the first time.Has anyone seen this before? This comes up after verilator has been installed and it is trying to install NyuziToolChain.
The text was updated successfully, but these errors were encountered: