-
Notifications
You must be signed in to change notification settings - Fork 17
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
Can not build with F#4.0/VS2015 - FS3186 error reading F# metadata node #43
Comments
Have you tried building FsControl itself with F# 4.0 ? |
Same error building FsControl. Sorry, should have done that first. :-\ Trying to build with F# 4.0:
|
So you're using the F# 4.0 compiler but apparently FSharp.Core.dll is still the one for F# 3.1 ? Could you confirm that, and if that's the case compile against https://www.nuget.org/packages/FSharp.Core/4.0.0.1 instead? |
I get the same or similar warning, when trying to compile FSharpPlus on Linux. I just cloned the repo and executed the following command line:
To me it seems like I am compiling against FSharp.Core 4.3.0. |
I don't know if those warnings will result in any compile or runtime error. I tried to rebuild the project in myget, it seems now they updated their compiler to the one from VS2015 because now I get those warnings there too. |
I get those warnings and after that the compilation process seems to hang in some infinite loop with 100% CPU usage. If you have an idea how to investigate that further, do tell me. |
Be aware that the project takes some time to compile, the last build I did took about 14 mins in myget. |
That was indeed the case, I just did not wait long enough. Thanks! |
Submitted an issue to the F# compiler. |
I have a feeling that this is going to be difficult to sort out, as I can't reproduce it in a new project. I thought I'd report it in case you had any tips for me to work around it.
I have a project that depends on Fleece. The build fails on VS2015/F#4.0 with the following error:
Dependencies:
Builds fine with Microsoft Build Tools 2013 / VS2013.
Edit 2016-04-05:
Workaround: add nowarn.
The text was updated successfully, but these errors were encountered: