@jahway603 holy wow, that is a backtrace. It looks like maybe our version of Boost is incompatible with the compiler versions of 22.04, which seems to be gcc 11.2.0 . We can try to upgrade our boost dependency, but that also has the risk of requiring our code to change.
@jahway603 holy wow, that is a backtrace. It looks like maybe our version of Boost is incompatible with the compiler versions of 22.04, which seems to be gcc 11.2.0 . We can try to upgrade our boost dependency, but that also has the risk of requiring our code to change.
To fix this bug, we need to update info in depends/packages/boost.mk, which also has the bug of referring to our old Github(!) . We currently use boost 1.72 . Upstream Zcash uses 1.79 which is a good candidate to try in our code.
To fix this bug, we need to update info in `depends/packages/boost.mk`, which also has the bug of referring to our old Github(!) . We currently use boost 1.72 . Upstream Zcash uses 1.79 which is a good candidate to try in our code.
https://github.com/zcash/zcash/blob/master/depends/packages/boost.mk
Easiest thing is probably to replace the current boost.mk in hush3.git with the latest boost.mk from zcash.git and see if that works.
@jahway603 is this something you can try?
After updating boost to 1.79 with minor tweaks instead of just using zcash's boost.mk I get
checking for __gmpn_sub_n in -lgmp... no
configure: error: libgmp missing
which doesn't make sense as the libgmp.tar.gz is downloaded in hush3/built/x86_64-unknown-linux-gnu/libgmp/
After updating boost to 1.79 with minor tweaks instead of just using zcash's boost.mk I get
```
checking for __gmpn_sub_n in -lgmp... no
configure: error: libgmp missing
```
which doesn't make sense as the libgmp.tar.gz is downloaded in `hush3/built/x86_64-unknown-linux-gnu/libgmp/`
GCC 11 defaults to -std=gnu++17 instead of -std=gnu++14: the C++17 standard, plus GNU extensions. This brings several changes that users should be aware of. The following paragraphs describe some of these changes and suggest how to deal with them.
Some users might prefer to stay with gnu++14, in which case we suggest to use the -std=gnu++14 command-line option, perhaps by putting it in CXXFLAGS or similar variables in Makefiles.
Ok, I believe the "correct" fix is to force our compiling to use c++14 instead of c++17, which is the new default.
In zcutil/build.sh, we need to do this:
```
CONFIG_SITE="$PWD/depends/$HOST/share/config.site" ./configure "$HARDENING_ARG" "$LCOV_ARG" "$TEST_ARG" "$MINING_ARG" $CONFIGURE_FLAGS CXXFLAGS='-g -std=gnu++14'
```
We might need to update some other Makefiles, but that should make the build mostly complete.
https://gcc.gnu.org/gcc-11/porting_to.html
```
GCC 11 defaults to -std=gnu++17 instead of -std=gnu++14: the C++17 standard, plus GNU extensions. This brings several changes that users should be aware of. The following paragraphs describe some of these changes and suggest how to deal with them.
Some users might prefer to stay with gnu++14, in which case we suggest to use the -std=gnu++14 command-line option, perhaps by putting it in CXXFLAGS or similar variables in Makefiles.
```
Used update-alternatives and now have gcc-9 and g++-9 as Ubuntu 22.04 defaults for gcc/g++, but still bails.
Next thing I see different between the Ubuntu LTS are the version of make used, but not sure if that could be the issue or not.
Ubuntu version
GNU Make Version
22.04
4.3
22.04
4.2.1
18.04
4.1
Tried updating our boost.mk with lines 2 thru 5 (4 lines) so it downloads newer boost 1.79 instead of 1.72. It makes it past the rust compiling portion, but I get the same checking for __gmpn_sub_n in -lgmp... no
& configure: error: libgmp missing I saw above that I initially reported; so maybe it's a boost thing with that version that must need newer version of libgmp? Idk.
Checked against Zcash and Komodo; libgmp comes from KMD-upstream and not in zcash
Checked Zen and Zclassic and they use much older versions of boost, but same version of libgmp
* Used update-alternatives and now have gcc-9 and g++-9 as Ubuntu 22.04 defaults for gcc/g++, but still bails.
* Next thing I see different between the Ubuntu LTS are the version of make used, but not sure if that could be the issue or not.
| Ubuntu version | GNU Make Version |
|-------|-------|
| 22.04 | 4.3 |
| 22.04 | 4.2.1 |
| 18.04 | 4.1 |
* Tried updating our boost.mk with lines 2 thru 5 (4 lines) so it downloads newer boost 1.79 instead of 1.72. It makes it past the rust compiling portion, but I get the same `checking for __gmpn_sub_n in -lgmp... no`
& `configure: error: libgmp missing` I saw above that I initially reported; so maybe it's a boost thing with that version that must need newer version of libgmp? Idk.
* Checked against Zcash and Komodo; libgmp comes from KMD-upstream and not in zcash
* Checked Zen and Zclassic and they use much older versions of boost, but same version of libgmp
Here's the [Boost changelog](https://www.boost.org/doc/libs/1_79_0/libs/log/doc/html/log/changelog.html) & the [Boost version histories](https://www.boost.org/users/history/) as maybe we need a version somewhere between 1.72 and 1.79 for it to work on 22.04?
@jahway603 I wonder if this compiles under clang on Ubuntu 22.04 and that could be a workaround. Tell people to use clang for now to compile on that version of Ubuntu.
@jahway603 I wonder if this compiles under `clang` on Ubuntu 22.04 and that could be a workaround. Tell people to use `clang` for now to compile on that version of Ubuntu.
Tested more Ubu 22.04 fun! There's some magic happening in my branch right now, as it's working with gcc/g++ v9 (alternative) but still fails with the defaultly installed gcc/g++ v11
With gcc9/g++9 as the default compiler:
Branch
Status
Master
Fail
Dev
Fail
Jahway603
SUCCESS
With gcc11/g++11 as the default compiler:
Branch
Status
Master
Fail
Dev
Fail
Jahway603
Fail
Taking note here of the update-alternative commands to switch between gcc/g++ versions sudo update-alternatives --config gcc sudo update-alternatives --config g++ Link with info how to change this
Tested more Ubu 22.04 fun! There's some magic happening in my branch right now, as it's working with gcc/g++ v9 (alternative) but still fails with the defaultly installed gcc/g++ v11
With gcc9/g++9 as the default compiler:
| Branch | Status |
| ------ | ------ |
| Master | Fail |
| Dev | Fail |
| Jahway603 | **SUCCESS** |
With gcc11/g++11 as the default compiler:
| Branch | Status |
| ------ | ------ |
| Master | Fail |
| Dev | Fail |
| Jahway603 | Fail |
Taking note here of the update-alternative commands to switch between gcc/g++ versions
`sudo update-alternatives --config gcc`
`sudo update-alternatives --config g++`
[Link with info how to change this](https://linuxconfig.org/how-to-switch-between-multiple-gcc-and-g-compiler-versions-on-ubuntu-22-04-lts-jammy-jellyfish)
With gcc10/g++10 as the default compiler also had great success with latest jahway603 branch
Branch
Status
Master
Fail
Dev
Fail
Jahway603
SUCCESS
Just tried with gcc/g++ v10...
With gcc10/g++10 as the default compiler also had **great success with latest jahway603 branch**
| Branch | Status |
| ------ | ------ |
| Master | Fail |
| Dev | Fail |
| Jahway603 | **SUCCESS** |
Describe the issue
Unable to compile/build on Ubuntu 22.04, which was released recently.
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:
Expected behaviour
For it to compile/build correctly.
Actual behaviour + errors
It fails to compile/build.
The version of Hush you were using:
latest master branch
Machine specs:
Any extra information that might be useful in the debugging process.
@jahway603 holy wow, that is a backtrace. It looks like maybe our version of Boost is incompatible with the compiler versions of 22.04, which seems to be gcc 11.2.0 . We can try to upgrade our boost dependency, but that also has the risk of requiring our code to change.
To fix this bug, we need to update info in
depends/packages/boost.mk, which also has the bug of referring to our old Github(!) . We currently use boost 1.72 . Upstream Zcash uses 1.79 which is a good candidate to try in our code.https://github.com/zcash/zcash/blob/master/depends/packages/boost.mk
Easiest thing is probably to replace the current boost.mk in hush3.git with the latest boost.mk from zcash.git and see if that works.
@jahway603 is this something you can try?
After updating boost to 1.79 with minor tweaks instead of just using zcash's boost.mk I get
which doesn't make sense as the libgmp.tar.gz is downloaded in
hush3/built/x86_64-unknown-linux-gnu/libgmp/Ok, I believe the "correct" fix is to force our compiling to use c++14 instead of c++17, which is the new default.
In zcutil/build.sh, we need to do this:
We might need to update some other Makefiles, but that should make the build mostly complete.
https://gcc.gnu.org/gcc-11/porting_to.html
Used update-alternatives and now have gcc-9 and g++-9 as Ubuntu 22.04 defaults for gcc/g++, but still bails.
Next thing I see different between the Ubuntu LTS are the version of make used, but not sure if that could be the issue or not.
Tried updating our boost.mk with lines 2 thru 5 (4 lines) so it downloads newer boost 1.79 instead of 1.72. It makes it past the rust compiling portion, but I get the same
checking for __gmpn_sub_n in -lgmp... no&
configure: error: libgmp missingI saw above that I initially reported; so maybe it's a boost thing with that version that must need newer version of libgmp? Idk.Checked against Zcash and Komodo; libgmp comes from KMD-upstream and not in zcash
Checked Zen and Zclassic and they use much older versions of boost, but same version of libgmp
Here's the Boost changelog & the Boost version histories as maybe we need a version somewhere between 1.72 and 1.79 for it to work on 22.04?
@jahway603 I wonder if this compiles under
clangon Ubuntu 22.04 and that could be a workaround. Tell people to useclangfor now to compile on that version of Ubuntu.@jahway603 do you still see these same problems on the latest master branch?
@duke just tried it with latest master branch and it still chokes & dies. I don't know how to change it to try clang, so it's using gcc.
Tested more Ubu 22.04 fun! There's some magic happening in my branch right now, as it's working with gcc/g++ v9 (alternative) but still fails with the defaultly installed gcc/g++ v11
With gcc9/g++9 as the default compiler:
With gcc11/g++11 as the default compiler:
Taking note here of the update-alternative commands to switch between gcc/g++ versions
sudo update-alternatives --config gccsudo update-alternatives --config g++Link with info how to change this
Just tried with gcc/g++ v10...
With gcc10/g++10 as the default compiler also had great success with latest jahway603 branch
Fixed by PR #282, so closing