Open ducky64 opened 6 years ago
Are you using an IDE? We've previously had similar issues on MacOS using IntelliJ
No, this is with just sbt.
I can reproduce it on my Windows 10 machine. All it takes is a fresh clone followed by a sbt assembly
.
I have the same problem on my Windows 10 machine with fresh installed Oracle JDK8 and SBT tools.
I have the same problem ,anyone know how to solve it
I haven't found a good solution, but here are some workarounds:
I have the same problem on win7 and fedora29. and get a temporary solution from a kind-hearted guy, and I also share it with you. When the error comes up compiling firrtl, remove other files except FirrtlProtos.java in firrtl\target\streams\protobuf\protobufGenerate\$global\streams\protobuf_2.12\out-cache, then re-compile, it will pass and you will notice the java files to be compiled are reduced from 9 to 5. Hope anyone can find the root cause for this problem.
I have the same problem on win7 and fedora29. and get a temporary solution from a kind-hearted guy, and I also share it with you. When the error comes up compiling firrtl, remove other files except FirrtlProtos.java in firrtl\target\streams\protobuf\protobufGenerate$global\streams\protobuf_2.12\out-cache, then re-compile, it will pass and you will notice the java files to be compiled are reduced from 9 to 5. Hope anyone can find the root cause for this problem.
It may compile but it doesn't pass the tests.
sbt -mem 2048 ++2.11.12 publishLocal
The problem can be solved by using AdoptOpenJDK prebuild windows binaries. I got the same problem when I use Oracle JAVA 1.8.0_231 in my win10 x64 machine. After installing AdoptOpenJDK 1.8.0_242 instead, the build was successful.
I get this error while trying to compile firrtl in sbt under Windows on two different machines. However, firrtl compiles fine under Linux, even using WSL on the same machine. I tried blowing away the entire firrtl repository as well as the entire .ivy2 cache and versions of firrtl in the .ivy2 local.
Anyone else have issues building firrtl under Windows?
Type of issue: bug report
If the current behavior is a bug, please provide the steps to reproduce the problem:
What is the use case for changing the behavior?
Impact: unknown
Development Phase: something is broken and I don't know what
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. Stack Overflow, gitter, etc) See above for stack trace.