-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build error: incompatible pointer type #6320
Comments
Yes, it's a gcc 14 incompatibility. status-im/nim-stint#153 resolves the |
The remaining issue here is the KZG library. The fix for that did not make it into the upcoming release ( Keeping issue open because it'll still be an |
Indeed, the error persists on |
Basically two remaining steps:
It's plausible but not guaranteed that these will happen in time for v24.7.0. In theory everything necessary now exists, it's integrating and having enough time to test it. |
#6403 fixes this, but refraining from closing this issue until we test it some more. |
Unfortunately, the issue seems to persist on my side:
Full output: https://pastebin.com/RvstWPke Please let me know if I should open a new issue or if you need anything else from me. |
v24.6.0 doesn't support this, but v24.7.0 (imminent) will. The fix was applied, not released. If you want to try this, check out the |
Description
When building from source, the command
make -j4 nimbus_beacon_node
fails with a compilation error in dependencynim-stint
:To Reproduce
Just follow the normal steps to build from source:
$ git clone https://github.com/status-im/nimbus-eth2 $ cd nimbus-eth2/ $ make -j4 nimbus_beacon_node
Tested with
v24.5.1
,v24.5.0
andv24.4.0
, all yield the same results.Using up-to-date Arch Linux on a 2021 Intel NUC.
Results
Full, unmodified output: https://pastebin.com/SsqbBnn5
Additional context
v24.4.0
compiled well on my machine a few weeks ago when it was released. When I tried to compilev24.5.1
a few days ago, this compilation error happened, and after trying multiple things, I realized it was now happening onv24.4.0
as well. This might suggest the issue is on my side. However, this is a dedicated hardware for running a full node and not much else.The text was updated successfully, but these errors were encountered: