-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
llvm missing #194
Comments
Do you know where bb31aec2cc85b6e2e85e687d086f85408b166c42 is coming from? It doesn't look like the src/llvm-project directory was ever pinned to that revision. The following command shows nothing:
The current revision we are pinned to is |
Hello, |
I'm a little confused, why are you trying to close BTW that command ( |
Sorry I copied that from the command line. I initially tried git clone —recourse-sub modules https://github.com/Holzschuh/wasi-sdk.git, which gave me the error message. Subsequently I tried to clone llvm directly with the previous command |
Can you try again with |
❯ git clone --recurse-submodules https://github.com/holzschu/wasi-sdk.git |
The problem is that your fork of It would have been useful if you could have mentioned from the beginning that it was your own fork that you were cloning and included the full command and output in the original report. |
I am not sure how that happened even though I did download the repo previously. Also I do not understand how the change ended up anywhere in the github repo |
my sincere apologies. Today is not my day. I did not notice that I landed in the WebAssembly Github Repo. I was under the impression it is the repo I cloned from. |
Hello,
I am getting an error message on clone:
From https://github.com/llvm/llvm-project
5c52753d9ff2..7b424b933355 main -> origin/main
fatal: remote error: upload-pack: not our ref bb31aec2cc85b6e2e85e687d086f85408b166c42
Fetched in submodule path 'src/llvm-project', but it did not contain bb31aec2cc85b6e2e85e687d086f85408b166c42. Direct fetching of that commit failed.
The text was updated successfully, but these errors were encountered: