freechipsproject / chisel-bootcamp

Generator Bootcamp Material: Learn Chisel the Right Way
Apache License 2.0
981 stars 278 forks source link

Local install for bootcamp into Windoze 10 reporting errors? #117

Closed Bazmundi closed 4 years ago

Bazmundi commented 4 years ago

Running Java 8 as build 1.8.0_261-b12 on Windoze 10.

As per instructions for windoze 10.

Downloaded coursier.

Ran the following in cmd prompt (as per instructions with coursier in directory "C:\Users\pierc\dev\jupyter\jupyter-scala"):

cmd1

C:\Users\pierc\dev\jupyter\jupyter-scala>java -noverify -jar coursier launch -r jitpack -i user -I user:sh.almond:scala-kernel-api_2.12.8:0.2.1 sh.almond:scala-kernel_2.12.8:0.2.1 --sources --default=true -- --install

Got the following:

Downloaded 1 missing file(s) / 1
Unrecognized argument: --sources
Unrecognized argument: --default=true

I removed "--sources --default=true" from command line in cmd shell to run:

cmd2

java -noverify -jar coursier launch -r jitpack -i user -I user:sh.almond:scala-kernel-api_2.12.8:0.2.1 sh.almond:scala-kernel_2.12.8:0.2.1  -- --install   

That previous line appeared to run.

Problematic is I found scala folder "C:\Users\pierc\AppData\Roaming\jupyter\kernels" where you would expect it. But its empty?

Certainly, when I ran jupyter lab it found no scala kernel.

When I try running the cmd2 again it obviously reports scala already installed.

So I use the --force option as the script suggests and ran:

cmd3

java -noverify -jar coursier launch -r jitpack -i user -I user:sh.almond:scala-kernel-api_2.12.8:0.2.1 sh.almond:scala-kernel_2.12.8:0.2.1  -- --force --install   

The command above removes the empty scala folder from the AppData path, but it drops out with:

Error: C:\Users\pierc\AppData\Roaming\jupyter\kernels\scala

This happens each time I ran cmd3, so I ran cmd2 again which results in an error:

Error: Illegal char <:> at index 2: /C:/Users/pierc/dev/jupyter/jupyter-scala/coursier

This suggests either the coursier file gets corrupted during the run or a conditional section that is activated during this sequence has a bug in it.

So, I downloaded coursier again but still got the problem of the illegal char. So it appears the install process is now completely broken some how.

So:

  1. Install does not work using suggested cmd1 for Windoze .
  2. Inaugural run of cmd2 only creates an empty scala directory under kernels.
  3. The cmd2 script correctly reports scala "exists" if ran again (because it finds the empty directory).
  4. Using --force option (cmd3) happily deletes the empty directory but then raises error reporting the scala kernal directory path (whatever that is supposed to mean).
  5. Subsequently running the command cmd2 results in a error suggesting corruption of the coursier file, or at least a conditional section is run that has a bug in it on first inspection, but running against a fresh download of the coursier file sees the same problem.

Not sure then whether I have caused a problem because I dropped the --sources and --default parameters or the script is simply just broken.

Something somewhere may have been touched, that has to be untouched, to get around the illegal character problem?

The idea that you may need to adjust the script is great, if it was intuitive and did not break any re-install attempts.

So, I need first a hint to back out of the scala almond install please.

Then we can work our way back into why the command line does not work as described.

edwardcwang commented 4 years ago

Hey, thanks for your interest in Chisel and reporting this! I did some experiments just now, and indeed, what happened is that almond/coursier updated their interface and broke a bunch of things :(

I just pushed a fix to the Windows installation instructions and test them just now, and they seem to work. Please take a look and let me know if it works for you!

Note: at one point when (re-)installing the Scala kernel, you may need to append a --force at the end of the command.

Bazmundi commented 4 years ago

Brilliant! Thanks.

On Tue, 29 Sep. 2020, 09:05 edwardcwang, notifications@github.com wrote:

Hey, thanks for your interest in Chisel and reporting this! I did some experiments just now, and indeed, what happened is that almond/coursier updated their interface and broke a bunch of things :(

I just pushed a fix to the Windows installation instructions and test them just now, and they seem to work. Please take a look and let me know if it works for you!

Note: at one point when (re-)installing the Scala kernel, you may need to append a --force at the end of the command.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/freechipsproject/chisel-bootcamp/issues/117#issuecomment-700337772, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANQYK7MT6UAQRY4WB42VLTSIEMS3ANCNFSM4R3HET4Q .