-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Build fails on Mac/Linux/Windows #14644
Comments
It looks like you're having issues restoring the dependencies for Mac/Linux. The Linux problem is listed on the wiki: https://github.com/dotnet/corefx/wiki/Building%20On%20Unix. Try For the Mac/Windows we can look at it with more details- can you delete your /packages directory and follow the instructions on the wiki? Please describe exactly what you've done and what output you get. I assume for the Mac it just failed to download the Roslyn package (Microsoft.Net.ToolsetCompilers). Also helpful:
|
@JeremyKuhne For Linux, For Mac, when delete /packages directory and build, get the error For Windows, build corefx on another computer that has Visual Studio 2013, get more errors(see detail). |
Build failure on Mac is caused by network problem between China and NuGet server.
|
@cnblogs-dudu Thanks for the extra details. Looks like your issues are primarily related to network issues pulling down the required packages. @ericstj Some thoughts: Not sure what sort of retry configurability we have or will have, but here is an example of where retry functionality might be useful. Also, perhaps an initial step confirming the ability to even communicate with servers we know were going to hit? And maybe a more complete package audit as part of the build? Anything to get stronger feedback before compilation starts would help avoid confusion. :) |
Fix build failure on Windows by deleting bin directory in corefx and rebuilding. |
Fails on Mac OS X:
Fails on Linux CentOS:
Fails on Windows with VS2015:
33 errors, see https://gist.github.com/cnblogs-dudu/d74afabd6849121c395e
The text was updated successfully, but these errors were encountered: