-
Notifications
You must be signed in to change notification settings - Fork 288
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: 'abc' is not configured as a git submodule. #2298
Comments
What steps did you do before running the build script. This seems to be a git error and nothing platform specific. |
@jaejunllee
|
@maliberty |
@vvbandeira Thank you for your answer. |
@vvbandeira Could the name change be causing the problem? |
Can you just clone a new area? |
I didn't understand what you said, could you explain it to me in more detail? |
Just clone ORFS again in a new area as if for the first time. |
I tried again after cloning ORFS to a new region from scratch. Error : 'abc' is not configured as a git submodule. |
This is just a GH notation to indicate that Another thing that I found odd is the |
I run the command on the "/home/jjunjun/OpenROAD-flow-scripts/" |
Please give the exact sequence of commands you are giving from nothing to failure. |
Start at the following path : /home/jjunjun/
Please let me know if you need any further information |
I did these steps without error. Please try it in a fresh directory as I think you may have an older result that is interfering. Note that we don't build or test on Centos7 anymore as it is EOL. |
Subject
[Flow] for any util, flow Makefile, or flow script issues.
Describe the bug
When executing build_openroad.sh in a centos7.4 Linux environment, the following error message occurs.
Error : 'abc' is not configured as a git submodule.
Expected Behavior
I would like to know how to fix the error I shared.
Environment
To Reproduce
When executing build_openroad.sh in a centos7.4 Linux environment, the following error message occurs.
Error : 'abc' is not configured as a git submodule.
Relevant log output
No response
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: