You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The instructions for installing SymbiFlow found here state to download architecture definitions using the following command:
wget -qO- https://storage.googleapis.com/symbiflow-arch-defs-install/quicklogic-arch-defs-63c3d8f9.tar.gz | tar -xz -C $INSTALL_DIR/eos-s3/
However, upon doing this and attempting to build the examples, the following error is obtained.
(eos-s3) root@e28a048119eb:/test/symbiflow-examples/eos-s3# make -C btn_counter
make: Entering directory '/test/symbiflow-examples/eos-s3/btn_counter'
ql_symbiflow -compile -d ql-eos-s3 -P pd64 -v btn_counter.v -t top -p chandalar.pcf
make: ql_symbiflow: No such file or directory
make: *** [Makefile:10: all] Error 127
make: Leaving directory '/test/symbiflow-examples/eos-s3/btn_counter'
Poking around in $INSTALL_DIR/eos-s3/, it appears that the tarball is extracted to $INSTALL_DIR/eos-s3/quicklogic-arch-defs rather than $INSTALL_DIR/eos-s3/install as expected.
This issue doesn't exist with the xc7 architecture definitions because those have the files directly within the tarball whereas the eos-s3 tarball has the files within a directory within the tarball.
Several workarounds exist, but the one that is easiest for end users is to run the following:
The instructions for installing SymbiFlow found here state to download architecture definitions using the following command:
However, upon doing this and attempting to build the examples, the following error is obtained.
Poking around in
$INSTALL_DIR/eos-s3/
, it appears that the tarball is extracted to$INSTALL_DIR/eos-s3/quicklogic-arch-defs
rather than$INSTALL_DIR/eos-s3/install
as expected.This issue doesn't exist with the xc7 architecture definitions because those have the files directly within the tarball whereas the eos-s3 tarball has the files within a directory within the tarball.
Several workarounds exist, but the one that is easiest for end users is to run the following:
On the maintainer side, the eos-s3 architecture definition tarball should be updated to omit the containing directory.
The text was updated successfully, but these errors were encountered: