-
Notifications
You must be signed in to change notification settings - Fork 179
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
Cant build clear Ubuntu 22.04 both install and install-cmake fail for different reasons #741
Comments
@StormLord07 I've expanded the test matrix on my personal repository to cover Ubuntu 22.04 with gcc-12 and clang-14 as a demonstration of workability here. This leads me to believe there is some other environmental issue for the failures you are encountering. Signal termination implies either system limitation or user intervention. Is this the case for your use of Boost log related issue imply you have a competing version of boost installed which is being detected, potentially lacking the |
Under the above assumptions related to boost, I've incorporated the hint mechanism for FindBoost into the script found here. |
@pmienk, I can't be sure about running out of memory. But RAM did a spike to 80% load a few minutes before error, might look into increasing swap memory size. As for boost related issue, I'll check It, do I need to change something in the call of install-cmake.sh or all should work as is? |
@StormLord07 the linked updated script will consume |
@pmienk, will try to pass |
UPD: increasing swap file to 16 gigs did the job, everything works fine with |
I am facing a similar issue... I am using Ubuntu 22.04 on a aarch64 machine... and install.sh fails with the following error
I have installed libboost-all-dev package as advised elsewhere but no use. I even tried using |
@StormLord07 To be clear, |
@praveenbm5 It should be noted that the relevant documentation advised not to use the package if possible. Please advise if you're referring to Please elaborate by providing the script, parameterization, and any relevant environment information in order to allow us to address your issue properly. |
Thank you for the response @pmienk I tried using both methods Let me elaborate on install.sh method..
I have boost installed via libboost-all-dev and the libs can be found in
when this failed, I tried using the boost compiles and gets installed to
in both cases... i get the same error
both logs are attached for your perusal. |
@praveenbm5 It would be helpful to see the specific commands. From the logs, I take it that these were In order to reduce the conflict of locating boost in side by side installation, I highly suggest utilizing a userspace prefix directory. By providing |
@pmienk Maybe worth noting that only libbitcoin explorrer fails. |
command:
Error:
|
In the mean time, while we resolve this build issue, can you please share an aarch64 binary of bx you have built? |
@StormLord07 Thank you for the output. The fact that it's surfacing as a linker error may imply that the includes found and the libs are mismatched from detection. Is it possible you've attempted to install both versions of boost to the same path? That could have produced this issue and would have been disambiguated by a |
@praveenbm5 Congratulations, you're error is no longer related to cmake, boost, or the original autotools resource issue. This should be followed up with as a separate issue from this point. I will point you to here where the linker issue you're referring to has been brought up before and resolved. I do not have plans to make binaries available at this time. |
@pmienk |
@StormLord07 It's possible that the environment variable |
@StormLord07, sorry, |
@pmienk I'll test it as soon as i get to a quiet place, i think i'll log out the |
Thank you. I could compile successfully with the following command
|
I cloned The library, switch to version3
run
all was installed succesfully
run
got
while comiling algorythm.hpp in explorrer
Ok tried to cmake
got
UPD: clear Ubuntu 22.04 installation
The text was updated successfully, but these errors were encountered: