Unai Martinez-Corral

FTR, #822 might be related. Nevertheless, I'm glad @diogratia's workaround let you move forward!

> ``` > e: e.o a1.o a2.o > e.o: e.vhd > a1.o: a1.vhd e.o > a2.o: a2.vhd e.o a1.o > ``` What should happen if the user then edits file...

FTR, there is now a test for this feature in https://github.com/VHDL/Compliance-Tests/blob/main/vhdl_2008/tb_matching_case.vhd. Ref: VHDL/Compliance-Tests#19.

My guess is that you should not need to register the interpreter again after a docker system prune. Did you try it? When you register the interpereter the first time,...

Depending on the platform, it might not be possible to register binfmt formats. See the last item in https://dbhi.github.io/qus/development.html#roadmap. @jamesmortensen I believe that's what might be happening on GitPod, while...

> You don't mention aarch64 in the supported systems list We do list aarch64 as explicitly supported. The README says: > Ready-to-use docker images are provided for each of seven...

@bitcoinmeetups the example in the README will do: https://github.com/dbhi/qus?tab=readme-ov-file#setup ``` docker run --rm --privileged aptman/qus -s -- -p ``` That will register all foreign interpreters: i386 i486 alpha arm armeb...

The GUI is a different matter, not explicitly covered in this repository/project. The fact that GUIs cannot be executed on containers by default is a known limitation and lots of...

Can you show the output of `cat /proc/sys/fs/binfmt_misc/qemu-x86_64` after executing `docker run --rm --privileged aptman/qus -s -- -p x86_64`? Can you also please check which image of `aptman/qus` did you...

Can you show the output of `cat /proc/sys/fs/binfmt_misc/qemu-x86_64` after executing `docker run --rm --privileged aptman/qus -s -- -p x86_64`? Can you also please check which image of `aptman/qus` did you...