-
Notifications
You must be signed in to change notification settings - Fork 1.2k
git submodule update fails #1669
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
Comments
See here: This works fine for me so try not doing any recursive clone manually:
Edit: oh - that seemed to work for me yesterday but not today:
For the moment you may need to disable the shallow cloning:
|
Disabling the shallow cloning appears to have worked. Thank you!! |
Also confirming that this persists. Following @TommyMurphyTM1234's instructions from above does work temporarily. |
Thanks for the updates. As I mentioned, @mickflemm explains the issue here but, unfortunately, at the moment I don't really know what specific changes are needed in order to prepare a PR that fixes the problem. However @mickflemm did say that he hopes to be able to have a look again later this month. I presume that the CI builds will also fail next time that they run to create a release... |
Here the sed's for the above WA:
|
But I did not get any .gitmodule file when I cloned the github repository, should I just make the changes in the Makefile.in to overcome the failing of submodules? |
No. You need to ensure that the Note that files whose names start with a dot/period/'.' are often not visible by default to perhaps it's there but you're just not seeing it? Try |
To clarify... How it fails at the moment due to shallow clone issues:
Try again but this time apply the workaround:
|
The workaround (removing
|
I am trying to setup RISCV GCC toolchain on redhat. I have succesffuly set up it in ubuntu along with spike and proxyt kernel. But now with redhat I am facing issues with respect to cloning of the git.
Now if i follow the way told above it still fails
Please suggest me what to do |
You haven't done anything different in the second attempt that I can see so the results/failure are the same.
Please read my earlier post: In summary - to workaround the "shallow clone" problem for now do this:
|
gcc is started building by using this method, it is taking more time than usual but so far going great. Will update if it resolves the issue. Thanks alot |
@TVS2004Chaitanya - please do not post off topic additional issues about vector support in this thread. If necessary open a new issue. I have deleted the off topic posts. |
Please read my earlier post: In summary - to workaround the "shallow clone" problem for now do this:
|
It's worth noting that it seems like you have to delete and re-clone the entire repo. Yesterday I was following these same steps but just deleted the broken submodules which did not allow the workaround to work. |
Yes, that's why my instructions above show a clean/new clone of the repo rather than trying to use the workaround on the results of a previously failed clone. |
Fixed by this PR: |
This might be a re-opening of an old issue, or it may be new, not sure. Failing to grab submodules during make, and submodule update is failing as well. I have a local copy from last night that worked to use, but just wanted to bring this issue forward so it can get some attention (first time posting an issue to a big repo like this, sorry for any faux pas).
Edit to add: GCC and binutils have both thrown errors, but the script from issue 1654 shows only spike and pk are not advertised
The text was updated successfully, but these errors were encountered: