From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 14may2020
Date: Thu, 14 May 2020 14:48:42 -0700
Message-ID: <1AC048A7-FAD5-41EE-B4BF-F622F72EBAF8@getmailspring.com> (raw)
In-Reply-To: <CAPweEDy2_bBVfTFGyYAMvaTDDdxEmWR8jKRZOn7Z469ztvoswQ@mail.gmail.com>
Yesterday I worked on the script that automates the build and
installation of yosys and the various SYMByosys tools until when trying
to compile super_prove bitbucket had an internal error failed to load
for over half an hour. At that point I decided to try again the next
day. Today the bitbucket is working. I had to create two patches for the
abc-zz sub-dependency of super_prove, now super_prove compiles
successfully. Given that this prevents the successful compilation of an
entire yosys tool, should I make a PR with these small but significant
patches or should I just be satisfied that it now works for us and move
on? The abc-zz dependecy lives in a bitbucket repo
(https://bitbucket.org/niklaseen/abc-zz/src/default/) that is over five
years old and the super_prove bitbucket repo's
(https://bitbucket.org/sterin/super_prove_build/src/default/) most
recent commit is in 2017. Given this, what would you advise I do with
regard to a PR/moving on?
I'm hoping to finish the rest of the yosys tools in the script today,
and tomorrow finsish the rest of the HDL_workflow.
Cole
_______________________________________________
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: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 10:54 Luke Kenneth Casson Leighton
2020-05-14 14:23 ` Michael Nolan
2020-05-14 14:43 ` Luke Kenneth Casson Leighton
2020-05-14 15:49 ` Tobias Platen
2020-05-14 16:44 ` Luke Kenneth Casson Leighton
2020-05-14 18:28 ` Jacob Lifshay
2020-05-14 18:55 ` Luke Kenneth Casson Leighton
2020-05-14 21:48 ` Cole Poirier [this message]
2020-05-14 22:00 ` Michael Nolan
2020-05-14 22:29 ` Cole Poirier
2020-05-14 22:52 ` Luke Kenneth Casson Leighton
2020-05-14 22:42 ` Luke Kenneth Casson Leighton
2020-05-14 23:16 ` Yehowshua
2020-05-15 8:28 ` Luke Kenneth Casson Leighton
2020-05-15 9:07 ` Tobias Platen
2020-05-15 9:09 ` Luke Kenneth Casson Leighton
2020-05-15 9:13 ` Luke Kenneth Casson Leighton
2020-05-15 10:55 ` Luke Kenneth Casson Leighton
2020-05-15 11:19 ` Luke Kenneth Casson Leighton
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=1AC048A7-FAD5-41EE-B4BF-F622F72EBAF8@getmailspring.com \
--to=colepoirier@gmail.com \
--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