Installing via Magic script
I am following https://docs.modular.com/mojo/manual/get-started/ and using a
devcontainer in the process. (See https://github.com/jake-danton/mojo_test for reference).
I got it mostly working, but had some additional dependencies to install (build-essential, etc) to go from a clean Ubuntu setup (see repro for more info). So there may need to be either prerequisites added to the docs or an update to the script.
The two big things I haven't got working are:
* LLVM_SYMBOLIZER_PATH not being set (this should happen during installation, right?)
* The elf_dynamic_array_reader.h:64] tag not found error that many GitHub issues call out
Any insights to fixing these would be super helpful! Thanks!Get started with Mojo | Modular
Install Mojo and learn the language basics by building a complete Mojo program
GitHub
GitHub - jake-danton/mojo_test: Testing Mojo in a devcontainer
Testing Mojo in a devcontainer. Contribute to jake-danton/mojo_test development by creating an account on GitHub.
9 Replies
Afaik containerization for the stack is still new. I haven’t gotten into that yet
Mojo has been containerized for a while, a lot of the non-modular stdlib development used it before
magic existed.
If you crash the compiler, there will be missing debug info since the binary is stripped. That is likely what you are seeing.I didn’t know. I only know of it packaged with the magic image
But I meant Docker level containers in pure Mojo
What do you mean by that?
For example Docker is written in Go. An equivalent of Docker written in Mojo
I think there is very little reason to do that. Docker is one of those correctness-critical things where it's probably better to use a paranoid language like Rust than Mojo, but Docker is also never really in a hot path, so the main benefit would be reduced memory usage.
If the compiler crashes while running tests, it still shows the test results? Looking at it, I assumed it was just showing the stack trace of the test as if I copy paste it, I see another stack trace.
You might have also hit an assert with aborted the program.
Afaik, fixing
LLVM_SYMBOLIZER_PATH will not solve the error, but may give you better crash logs. This can be done by installing llvm: