Skip to content
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

Tools like Yosys and Vpr not in PATH on latest Quicklogic image #49

Closed
carlosedp opened this issue Dec 13, 2021 · 9 comments
Closed

Tools like Yosys and Vpr not in PATH on latest Quicklogic image #49

carlosedp opened this issue Dec 13, 2021 · 9 comments
Labels
bug Something isn't working $R/f4pga Related to `$R/f4pga` images and their dependencies

Comments

@carlosedp
Copy link
Contributor

❯ docker run -it --rm -v $(PWD):/src -w /src gcr.io/hdl-containers/symbiflow/eos-s3 yosys
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "yosys": executable file not found in $PATH: unknown.

❯ docker run -it --rm -v $(PWD):/src -w /src gcr.io/hdl-containers/symbiflow/eos-s3 vpr
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "vpr": executable file not found in $PATH: unknown.

Had to manually add with ENV PATH=/usr/local/envs/eos-s3/bin/:$PATH

@umarcor
Copy link
Member

umarcor commented Dec 13, 2021

You need to activate the conda environment after starting the container. See https://hdl.github.io/containers/ug/index.html#_symbiflow. However, that is tested for the xc7 images. As commented in the SymbiFlow channel on Slack, there might be issues in the eos-s3 image due to --strip-components: https://github.com/hdl/containers/tree/symbiflow-eos-s3.

@carlosedp
Copy link
Contributor Author

Doesn't work either... the conda script is using python which is not installed. There is python3 instead.

Also:

❯ docker run -it --rm -v $(PWD):/src -w /src gcr.io/hdl-containers/symbiflow/eos-s3
root@cbfcaa780bca:/src# python3 /usr/local/condabin/conda activate eos-s3

CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
To initialize your shell, run

    $ conda init <SHELL_NAME>

Currently supported shells are:
  - bash
  - fish
  - tcsh
  - xonsh
  - zsh
  - powershell

See 'conda init --help' for more information and options.

IMPORTANT: You may need to close and restart your shell after running 'conda init'.

@umarcor
Copy link
Member

umarcor commented Dec 13, 2021

I think I mistakenly kept the "old" URL (the one from June) when downloading the eos-s3 artifacts. I.e., I updated the xc7 URLs only: ee7ca86
Hence, that might have been fixed upstream. I will look into it as well.

@umarcor umarcor added bug Something isn't working $R/f4pga Related to `$R/f4pga` images and their dependencies labels Dec 14, 2021
@umarcor
Copy link
Member

umarcor commented Dec 14, 2021

It should be fixed now: 9958d93. Note that you need to use a login (probably interactive) shell in order to have the profile.d scripts properly sourced. See umarcor/f4pga-examples@a16becb and https://github.com/umarcor/symbiflow-examples/actions/runs/1576528548.

@umarcor umarcor closed this as completed Dec 14, 2021
@carlosedp
Copy link
Contributor Author

I don't get why adding this complexity to it.
I think this wouldn't work correctly with Edalize running thru the wrapper script as it calls each tool (symbiflow_synth, symbiflow_pack, etc) and the wrapper script assumes the tools are already in the path.

As we have different images for each FPGAZ toolchain, why not having the environment already activated.

@umarcor
Copy link
Member

umarcor commented Dec 16, 2021

Images are now available in the */conda/* namespace, and the environments are activated through profile.d. See:

@carlosedp
Copy link
Contributor Author

Running Edalize thru this new wrapper works: https://gist.github.com/carlosedp/ac36e9052bfa23f84b2f42f1a05ee1bd

@umarcor
Copy link
Member

umarcor commented Jan 17, 2022

@carlosedp
Copy link
Contributor Author

I'll probably submit a PR to el_docker script in Edalize and then I send there with the correct link :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working $R/f4pga Related to `$R/f4pga` images and their dependencies
Projects
None yet
Development

No branches or pull requests

2 participants