Skip to content
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

Guidance: git submodule update --init --recursive (Resource temporarily unavailable) #1264

Closed
phfbfc opened this issue Jun 14, 2019 · 6 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Resolution-Answered Related to questions that have been answered

Comments

@phfbfc
Copy link

phfbfc commented Jun 14, 2019

Followed README and build instructions from issue 489.
Got stuck at:
git submodule update --init --recursive
Which yielded:
0 [main] sh 6324 fork: child 1504 - died waiting for dll loading, errno 11
/mingw64/libexec/git-core/git-sh-setup: fork: retry: resource temporarily unavailable
To fix this, I attempted the following recommendation mentioned here, and modified the input like so:
npm uninstall -g submodule
npm cache clean
npm install -g submodule@latest
Taking this step provided output that looked promising, so I attempted the build, which failed because of the missing wil/Common.h

I'm looking to get past build, and based on other issues, it sounds like the git submodule update --init --recursive is my roadblock. Any help would be appreciated - thanks for your consideration.

@phfbfc phfbfc added the Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs label Jun 14, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 14, 2019
@zadjii-msft
Copy link
Member

This sounds like a git issue. Is it unique to the Terminal repo, or can you not init submodules for any git repo?

I'd look in #489, and follow up in the issue tracker for wherever you got git from.

@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs labels Jun 14, 2019
@DHowett-MSFT
Copy link
Contributor

Also, would you mind trying actual git for windows? It looks like this is mingw64's git, and I don't know how npm is getting involved here ...

@burhan
Copy link

burhan commented Jun 16, 2019

Try using the github desktop, cloning the repository there and then following the steps.

@squeeter
Copy link

Also, would you mind trying actual git for windows? It looks like this is mingw64's git, and I don't know how npm is getting involved here ...

@DHowett-MSFT: Good call on git for windows - I overlooked that this machine was running a different setup. As for npm, I was looking for solutions based on similar errors. At the time, I thought it was a git built-in.

@squeeter
Copy link

squeeter commented Jun 17, 2019

Uninstalling/Reinstalling git solved this issue.

@DHowett-MSFT
Copy link
Contributor

Thanks for testing.

@DHowett-MSFT DHowett-MSFT added Resolution-Answered Related to questions that have been answered and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

6 participants