On Sat, 2025-03-15 at 19:52 +0000, Scott Ashcroft wrote: > OK. I've managed to get an sbuild environment working by using the orig > tar file from the YosysHQ github. > The documentation issues are fixed up and I'm running what is hopefully > the final test build now. >
The test build worked. If you cherry pick the four following commits from: https://salsa.debian.org/sashcroft/yosys 5f1c9942c4d26295f620535b8c9dd7da9df4aeb3 142b85a3c02af3b9646abdda8ff5b54d4d44385f b688f952624ac5ca74e3a0c46c85797d91873ddd 306735c164c350a85bb2cb44168582e316974ee7 That should get everything working. (I'll do a merge request if you want but only if that's easier for you) Running the build properly in sbuild made the errors reasonably easy to fix. Thanks for your help with all of this. The python stuff was just the include path. By fixing it for post- install use we'd broken it for use during the build. Now it runs correctly I had to make sure dh_missing didn't moan about the python cache files which are created but not installed. The sphinx warnings were mostly due to use of rsync in another Makefile. I've patched it to use cp in a similar way to your patch. Getting that working revealed the docs build was trying to download some graphics from github. I've patched those calls out. I've also partially reverted the || rm $@@ patch as some of the commands intentionally error out when called with --help. Cheers, Scott
