-
Notifications
You must be signed in to change notification settings - Fork 78
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
/opt/symbiflow/xc7/install/bin/symbiflow_synth: line 93: prjxray-config: command not found + "ERROR: No such command: tcl" #154
Comments
as a side note, ./litex_setup.py install is not hermetic, it needed sudo and installed a bunch of stuff in my system python. Not sure if that was the intent. |
Hi @marcmerlin, I think that the problem here is that you did not source the conda environment, where Another hint that this might be the case is that you required sudo to install litex, which should not happen if it was to be installed in the conda environment. |
@acomodi thanks for the reply.
which seems to say it's using the wrong python again That said, I see you just removed the entire block I was having issues with So, should I just give up on this entire litex checkout that was out of tree and seemed a bit out of place (it wasn't clear why it was there, or how it plugged in with the next step) |
So, can you confirm that
|
Hi, I'm following the doc on https://symbiflow-examples.readthedocs.io/en/latest/building-examples.html and the first 2 examples work fine, but litetx is not as clear.
First "Linux LiteX demo" doesn't make it clear if I should be inside the symbiflow-examples git checkout to create all those things done by litex_setup, or elsewhere.
I made a need litex directory. The build then fails with
I do have this, but it's not in my path:
Your code added this to my path: /opt/symbiflow/xc7/conda/condabin:/opt/symbiflow/xc7/install/bin
I had to do this:
sauron:~/fpga/litex/litex-boards/litex_boards/targets$ export PATH="$PATH:$INSTALL_DIR/$FPGA_FAM/conda/envs/$FPGA_FAM/bin/"
but then:
The text was updated successfully, but these errors were encountered: