Closed TheLastCicada closed 2 years ago
Seems related to this issue https://github.com/pyinstaller/pyinstaller/issues/6993
On my test machine (arm64, ubuntu 20.04) removing the /opt/chia/libstdc++.so.6
file and then trying again solved the problem, but its not clear at this point if we'll run into issues with other supported platforms doing this.
Broken for me on the following versions (testing more):
Seems like this used to work for some of these older versions (per discussion with Zach) so maybe this is an issue with updated libstdc++ on the systems this is being installed on, and not being in sync or something with the version in the build image?
Building from a 20.04 based docker image instead of the 18.04 based docker image resolved the issue for me, at least on 20.04 - I believe Zach will test 22.04 and report back.
On my test machine (arm64, ubuntu 20.04) removing the
/opt/chia/libstdc++.so.6
file and then trying again solved the problem,
Thanks! Removing this lib solved the issue for me. x86_64, Ubuntu 20.04
Did some investigating. From what I can tell, this was caused by the switch from the github provided 18.04 runners for intel debs to the docker container (since the 18.04 runner image from github is now deprecated). GitHub provided newer versions of g++ than we have in our builder container (they added 9 and 10), and 9 provides the version of the gnu c++ lib that madmax is expecting. This means (and I confirmed by spot checking an older release) that the arm64 deb has likely never actually worked with madmax.
Testing a fix by adding g++ 9 and 10 to our builder image in the same manner that github used to install in their 18.04 image https://github.com/Chia-Network/build-images/pull/24 🤞
This is resolved now for future builds. The current release (1.6.0) still has the issue, but new builds and future releases should be fixed.
If you're using madmax and hitting this issue, you are likely ok to delete the library bundled with chia (/opt/chia/libstdc++.so.6
) as long as your system has a copy installed that supports the required CXX version (but do so at your own risk). To check, you can do something like the following:
x86_64
strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX_3.4.26
GLIBCXX_3.4.26
ARM64
strings /usr/lib/aarch64-linux-gnu/libstdc++.so.6 | grep GLIBCXX_3.4.26
GLIBCXX_3.4.26
As long as GLIBCXX_3.4.26
shows up in the output of the command (vs it being an empty result) you should have a system version installed that meets the requirements. (if strings is not installed, that can be installed with apt-get install binutils
)
What happened?
I've been plotting reliably with Madmax for a few months and yesterday upgraded to 1.5.1. Now when I run my same plotting command, I get the following error:
The plotting command I'm using is (sensitive data has been anonymized):
I'm installing the
chia-blockchain-cli
package viaapt
using the instructions from here https://github.com/Chia-Network/chia-blockchain/wiki/INSTALL#install-using-the-repository.Operating System:
Ubuntu is fully patched.
When I removed Madmax and tried reinstalling it with
chia plotters install madmax
, I get a similar error:UPDATE: Madmax installation works if I install from source. Madmax installation does NOT work if I install from the apt repository.
Version
1.5.1
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output