-
Notifications
You must be signed in to change notification settings - Fork 259
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
Could anyone install it on Ubuntu 22.04 #472
Comments
So were you able to install it on ubuntu 22.04? |
No. I switched to 18.04, and the installation is success. (However, other problems occur so I still cannot run it.) Some notes:
|
我在ubuntu22上安装好了。其中遇到了几个困难,第一个是git clone失败,因为网络封锁。 第二个是make的时候一个hpp文件中缺少include 查看报错里面有提到如何导入include |
用的是gcc-9 g++9 |
你遇到的情况跟我第二项一样 看这一条报错 |
so were you able to fix it in the end? |
I know it is assumed to be installed on 18.04, but I tried to install it on an Ubuntu 22.04 VM. (18.04 is too old for my project)
Does anyone successfully install it?
I tried to run
CC=gcc-7 CXX=g++-7 sudo -H pip3 install -e blockscipy
according to https://citp.github.io/BlockSci/setup.html#running-a-full-nodeBunch of unreadable errors like
/usr/include/blocksci/core/raw_address.hpp:18:9: error: ‘uint32_t’ does not name a type
... etc. I didn't read all but seems another C++ version problem:Btw, here are what I have done to resolve some version problems, maybe somebody can get some hints?
For
git clone https://github.com/citp/BlockSci.git
,--recursive
flag should be added. Otherwise later steps would complain files missing.git clone --recursive https://github.com/citp/BlockSci.git
gcc-7
andg++-7
are unavailable in Ubuntu 22.04, and trying to use later version of gcc could cause problem. Without changing the code, all I could do is to install them from this trick: https://askubuntu.com/questions/1406962/install-gcc7-on-ubuntu-22-04cmake
command also cause problem due to versioning. Latestcmake
is already much later thancmake 11
. So I build it from source: https://cmake.org/download/Any comments are welcome! Thank you.
The text was updated successfully, but these errors were encountered: