error when try to use fusesoc build atlys

[KarlTao]

Hey there,
I am trying to build core for atlys board, and I got this error:
WARN: File ../orpsoc-cores/systems/atlys/bench/orpsoc_tb.v does not exist
WARN: File ../orpsoc-cores/systems/atlys/bench/uart_decoder.v does not exist
ERROR: Failed to build FPGA: Command 'xtclsh' not found. Make sure it is in $PATH
While I have sourced setting64.sh and can run xtclsh directly from terminal.
I also added
export PATH=/opt/Xilinx/14.6/ISE_DS/common/bin/lin64:$PATH
export PATH=/opt/Xilinx/14.6/ISE_DS/ISE/bin/lin64:$PATH
to .bashrc.
Do you have a clue what is this issue about?
Thanks!
Karl

[olofk]

This is strange. The warnings are harmless, but I can't understand why it can't find the tools if you have sourced the correct settings file. I just tried it myself and don't have this problem.

Could you try to run the following lines as a python script to see if you get an error

import subprocess
subprocess.check_call(['xtclsh', '-h'])

[KarlTao]

Hi,
I ran the command you said, and here is the result:

Release 14.7 - xtclsh P.20131013 (lin)
Copyright (c) 1995-2013 Xilinx, Inc. All rights reserved.
xtclsh - Invoke tclsh in a interactive mode.
xtclsh -h - Print out the usage and version info and
exit.
xtclsh <Tcl_script> [arg1] ... [argn] - Evaluate the Tcl script with the
optional arguments and exit.

[olofk]

ok, that's odd. This is basically what fusesoc does internally. I don't have a clue for what's wrong. Just in case, you could remove the PATH lines from .bashrc. They shouldn't be needed if you source settings64.sh correctly

What OS and python version are you running?

[KarlTao]

Hi,
Thank you for replying, I solved it by running fusesoc init again, it downloaded some additional files. But it is odd since I have tried to build it on several different computers, and none of them worked after running fusesoc init once...
Anyway, Thank you very much for your answer.

[olofk]

Happy to hear that it worked out in the end even though I still don't know what was wrong.

I'm closing this now, but will check for potential problem with the init command, and also see if there are any other problems that could lead to the error message that you got. Thanks for reporting