From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
Date: Tue, 12 May 2020 19:41:04 +0000
Message-ID: <bug-291-13-UDKA6eiNlq@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #2 from Cole Poirier <colepoirier@gmail.com> ---
Luke, I was able to get the script to work to the point of correctly installing
and configuring the coriolis chroot such that it would open the coriolis window
diplaying the chicken, which when clicked on a few times displayed the coriolis
layout window as on the HDL workflow wiki. Unfortunately my script no longer
reaches this point of successful completion, and I am now consistently getting
stuck at this error:
```
-- CORIOLIS_TOP is set to
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install
-- Components of CORIOLIS_DIR_SEARCH:
-- /home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install
-- Found CORIOLIS_PYTHON:
--
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install/lib64/libpycrlcore.so
-- Configuring done
-- Generating done
-- Build files have been written to:
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/build/unittests
Make/Ninja command: ['make', '-j4', 'install']
Scanning dependencies of target unittests
[ 50%] Building CXX object src/CMakeFiles/unittests.dir/unittests.cpp.o
[100%] Linking CXX executable unittests
[100%] Built target unittests
Install the project...
-- Install configuration: "Release"
-- Installing:
/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install/bin/unittests
-- Set runtime path of
"/home/ace/coriolis-2.x/Linux.x86_64/Release.Shared/install/bin/unittests" to
""
Traceback (most recent call last):
File "./cgt", line 23, in <module>
helpers.showPythonTrace( sys.argv[0], e )
NameError: name 'helpers' is not defined
```
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 21:42 [libre-riscv-dev] [Bug 291] New: " bugzilla-daemon
2020-04-21 21:46 ` [libre-riscv-dev] [Bug 291] " bugzilla-daemon
2020-05-12 19:41 ` bugzilla-daemon [this message]
2020-05-13 0:09 ` bugzilla-daemon
2020-05-13 0:15 ` bugzilla-daemon
2020-05-13 0:16 ` bugzilla-daemon
2020-05-13 1:19 ` bugzilla-daemon
2020-05-13 2:00 ` bugzilla-daemon
2020-05-13 9:19 ` bugzilla-daemon
2020-05-13 17:58 ` bugzilla-daemon
2020-05-15 21:18 ` bugzilla-daemon
2020-05-18 20:26 ` bugzilla-daemon
2020-05-18 20:30 ` bugzilla-daemon
2020-05-18 20:37 ` bugzilla-daemon
2020-05-18 21:02 ` bugzilla-daemon
2020-05-18 22:15 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-291-13-UDKA6eiNlq@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git