Ubuntu 18.04 LTS Support #835

ryanRfox · 2018-04-09T14:02:28Z

jmjatlanta · 2018-04-09T15:29:40Z

I was able to compile and run bitshares-core on Ubuntu 18.04 (latest daily build) with the following caveats:

The bitshares-fc and bitshares-core branch openssl-1.1-support was used
~~The changes in bitshares-fc branch boost_1.65 was also merged in.~~

With a fresh install of Ubuntu 18.04, the following additional packages are necessary:
sudo apt install gcc g++ git cmake libboost-all-dev libssl-dev autoconf libcurl4-openssl-dev

Note 1: With a brand new install of git, certain commands may prompt you to do extra steps, such as git --global user.email or something similar. Read carefully, and follow their instructions.

Note 2: Certain git commands may open an editor, and ask you for a comment. There is no need to add a comment. [CTRL]+[X] will allow you to exit the editor and the process should continue normally.

Once the openssl-1.1-support ~~and boost_1.65~~ branches are merged in to bitshares-fc and bitshares-core, getting the source code will be easier. But until then, the instructions are:

git clone https://github.com/bitshares/bitshares-core.git
cd bitshares-core
git checkout openssl-1.1-support
git submodule update --init --recursive
cd libraries/fc
git checkout openssl-1.1-support
~~git pull https://github.com/jmjatlanta/bitshares-fc.git boost_1.65~~
cd ../../
cmake -DCMAKE_BUILD_TYPE=Release .
make

Update 2018-05-04: boost 1.65 changes merged in, adjusted instructions

ryanRfox · 2018-04-09T18:19:18Z

I successfully built the project using the steps outlined in the comment above. Next, I intend to build again for the TESTNET, then run my witness_node on the 18.04 OS for further testing.

abitmore · 2018-04-09T22:10:03Z

While this is a good to have feature and the correct direction to go, I don't think it's very high priority. After Ubuntu 18.04 is out, it may need some time for businesses to try it in production. My estimation on this is about 3-6 months.

operano02 · 2018-05-04T00:30:43Z

hi ;
can you explane the " boost_1.65 branches are merged in to bitshares-fc and bitshares-core, "
what does mean merged into ? how to merge into ? i'm newbie
after git pull https://github.com/jmjatlanta/bitshares-fc.git boost_1.65 command
" fatal: Couldn't find remote ref boost_1.65 " this error.

jmjatlanta · 2018-05-04T08:37:55Z

The work done on the boost_1.65 has now become part of the official bitshares-fc project. So, that line can be left out. I will adjust the post above.

jmjatlanta · 2018-05-12T21:43:02Z

To compile for the latest release of TESTNET ( instructions as of 12-May-2018 )

# Pull down the bitshares-core repository and place it in the directory
# bitshares-core (directory should not already exist)
git clone https://git@github.com/bitshares/bitshares-core
# Enter your new copy of the repository
cd bitshares-core
# checkout the testnet branch of bitshares-core
git checkout testnet
# checkout all the submodules needed
git submodule update --init --recursive
# merge in the openssl-1.1-support branch of bitshares-core
git pull https://github.com/bitshares/bitshares-core openssl-1.1-support
# move to the bitshares-fc directory
cd libraries/fc
# grab the latest, if you want to ( this is optional )
git checkout master
# merge in the openssl-1.1-support branch of bitshares-fc
git pull https://github.com/bitshares/bitshares-fc.git openssl-1.1-support
# go back to the bitshares-core directory
cd ../..
# prepare your Makefiles ( as you normally would )
cmake -DCMAKE_BUILD_TYPE=Release .
# compile the applications ( as you normally would )
make

abitmore · 2018-05-12T21:49:40Z

@jmjatlanta that means the only thing we need to do is to merge the OpenSSL 1.1 PR's?

We need to test:

sync testnet and mainnet,
connect a light wallet and make some transactions,
sign blocks and
etc.

jmjatlanta · 2018-05-12T21:58:46Z

@abitmore I have not tested the OpenSSL-1.1-support branch completely.

I would add that we need to test compiling with OpenSSL 1.0.2 with the 1.1-support branch merged in.

If we can get everything tested well and the 1.1-support branch merged in to the other branches, it would be a good win for those running 18.04 LTS, as they would not need anything beyond stuff they can apt-get plus the bitshares-core branch of their choice. The instructions above would be much shorter.

ryanRfox · 2018-05-13T11:27:33Z

I am failing to build at the same point with both OpenSSL 1.0.2g & 1.1.0g as demonstrated here:

@jmjatlanta I really appreciate the detailed instructions with inline comments above.

pmconrad · 2018-05-13T16:39:18Z

See #921, it includes the removal of these API calls

ryanRfox · 2018-05-31T16:34:56Z

Success! Yes, after commenting out the lines related to blind_sign API calls and deterministic_openssl_rand found in #921 the build completed without errors.

FrankBlabu · 2018-06-10T18:03:18Z

Are the instructions in the comments above still valid ? I get the reply "Couldn't find remote ref openssl-1.1-support" when trying to pull it.

I would appreciate any hint here. I updated my system to Ubuntu 18.04 without checking for the witness node compatibility before and now I'm stuck and cannot go back easily.

pmconrad · 2018-06-11T17:55:14Z

The branch has been merged into develop, please check out develop branch and build that. Don't forget to git submodule update --init --recursive.

ryanRfox · 2018-06-14T20:42:24Z

@FrankBlabu you may observe the build process for the develop branch provided by Travis-CI:
https://travis-ci.org/bitshares/bitshares-core/builds/391476199

Focus on lines 418 & 428:

git clone --depth=1 --branch=develop https://github.com/bitshares/bitshares-core.git
git submodule update --init --recursive

As needed, please open a Build Error Issue and complete the template with the relevant details:
https://github.com/bitshares/bitshares-core/issues/new?template=build_error.md

jmjatlanta · 2018-06-15T11:08:24Z

Updated instructions as of 15-June-2018 for develop branch, based on a fresh install of Ubuntu 18.04:

sudo apt install gcc g++ git cmake libboost-all-dev libssl-dev autoconf libcurl4-openssl-dev
git clone --branch=develop https://github.com/bitshares/bitshares-core.git
cd bitshares-core
git submodule update --init --recursive
cmake -DCMAKE_BUILD_TYPE=Release .
make

ying2025 · 2018-06-17T01:58:28Z

I have the similiar problem. But My openssl is 1.0.2. How I solve the following problems?
/home/zhr/bitshare/bitshares-core/libraries/deterministic_openssl_rand/deterministic_openssl_rand.cpp:92:1: error: invalid conversion from ‘void ()(const void, int)’ to ‘int ()(const void, int)’ [-fpermissive]
};
^
/home/zhr/bitshare/bitshares-core/libraries/deterministic_openssl_rand/deterministic_openssl_rand.cpp:92:1: error: invalid conversion from ‘void ()(const void, int, double)’ to ‘int ()(const void, int, double)’ [-fpermissive]
libraries/deterministic_openssl_rand/CMakeFiles/deterministic_openssl_rand.dir/build.make:62: recipe for target 'libraries/deterministic_openssl_rand/CMakeFiles/deterministic_openssl_rand.dir/deterministic_openssl_rand.cpp.o' failed
make[2]: *** [libraries/deterministic_openssl_rand/CMakeFiles/deterministic_openssl_rand.dir/deterministic_openssl_rand.cpp.o] Error 1
CMakeFiles/Makefile2:790: recipe for target 'libraries/deterministic_openssl_rand/CMakeFiles/deterministic_openssl_rand.dir/all' failed
make[1]: *** [libraries/deterministic_openssl_rand/CMakeFiles/deterministic_openssl_rand.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
zhr@ubuntu:~/bitshare/bitshares-core$ openssl version
OpenSSL 1.0.2g 1 Mar 2016

jmjatlanta · 2018-06-17T02:35:49Z

Hrmmm. It seems you are having a different problem @ying2025. Please create a new issue here:

https://github.com/bitshares/bitshares-core/issues/new?template=build_error.md

ying2025 · 2018-06-17T08:05:45Z

ubuntu:~/bitshare/bitshares-core$ git checkout openssl-1.1-support
error: pathspec 'openssl-1.1-support' did not match any file(s) known to git.

fvisconti · 2018-06-20T11:11:02Z

I'm on Ubuntu 18.04
openssl version: OpenSSL 1.1.0g 2 Nov 2017
followed all the steps mentioned by @abitmore, but facing the issue as in #409, which is said to be fixed on Ubuntu 17.10.
I configured with cmake -DCMAKE_BUILD_TYPE=Release as @jmjatlanta said.
Don't know exactly how to move (not even why this should work with Ubuntu 17.10 and not with 18.04).

jmjatlanta · 2018-06-20T11:19:11Z

On Ubuntu 18.04, things should work just fine if you are using the develop branch. In fact, it is slightly easier as there is no need to compile specific boost or openssl versions.

There must be some kind of problem (misconfiguration?) between doxygen and perl, if I am reading issue #409 correctly. I wasn't around when that issue appeared, so I can only speculate. Please post your build log and I'll see if I can help.

Note: Github messes with the formatting of the build log. I've found it better to post on something like pastebin.com and post a link here.

fvisconti · 2018-06-20T11:32:55Z

This is the last message in the build log.
In #409, they say to comment out lines in CMakeLists.txt, but I found they have been replaced in the develop branch..

[ 81%] Generating api_documentation.cpp
Can't locate doxygen/perlmod/DoxyDocs.pm in @INC (you may need to install the doxygen::perlmod::DoxyDocs module) (@INC contains: /hom
e/francesco/WORK/XXX/bitshares-core/libraries/wallet /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/per
l/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/li
b/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /home/francesco/WORK/XXX/bitshares-core/libraries/wallet/generate_api_docum
entation.pl line 6.
libraries/wallet/CMakeFiles/graphene_wallet.dir/build.make:62: recipe for target 'libraries/wallet/api_documentation.cpp' failed
make[2]: *** [libraries/wallet/api_documentation.cpp] Error 2
CMakeFiles/Makefile2:1826: recipe for target 'libraries/wallet/CMakeFiles/graphene_wallet.dir/all' failed
make[1]: *** [libraries/wallet/CMakeFiles/graphene_wallet.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

jmjatlanta · 2018-06-20T11:39:39Z

If you don't want to create the documentation, you could probably comment out line 4 of libraries/wallet/CMakeLists.txt like so...

# find_package( Doxygen )

I haven't tested it, but that should skip the documentation creation process. You'll have to re-run cmake, then run make, and let me know the results.

fvisconti · 2018-06-20T11:42:10Z

Ok, going to.

fvisconti · 2018-06-20T12:53:29Z

Builded succesfully, many thanks.

abitmore · 2018-06-20T13:20:23Z

If unable to find doxygen, build process should not fail, but skip the step gracefully.

By reading #409 and #479, it seems both doxygen and perl have been found, but the build is still failing? The #479 fix no longer works?

jmjatlanta · 2018-06-20T13:25:55Z

I agree @abitmore. A small clarification: the package doxygen is being found. The problem seems to be that sometimes it is not finding the perl module in libraries/wallet/doxygen/perlmod/DoxyDocs.pm. I do not know why it finds it on some boxes, but does not find it on others.

oxarbitrage · 2018-08-02T22:38:16Z

closing by work done before and final updating the docs at #1212
some testing was done by the core team today with ubuntu 18.01. gcc 7.3.0, boost 1.65.1(found in default installations) and everything looks good.

abitmore · 2018-08-02T22:45:21Z

Still some work to be done before final mainnet release. OP updated.

oxarbitrage · 2018-08-02T22:46:11Z

ok, got it, thanks.

abitmore · 2018-08-23T17:56:25Z

Done.

abitmore · 2018-10-31T21:03:57Z

Does the doxygen issue still exist? Will this help? steemit/steem@071f6a9

zhangbo-miuNEST · 2018-11-05T22:19:13Z

Does the doxygen issue still exist? Will this help? steemit/steem@071f6a9

It works.

ryanRfox added 2f Testing Status indicating the solution is being evaluated against the test case(s) and removed 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements labels Apr 9, 2018

abitmore mentioned this issue Jun 16, 2018

Problem with make! I need help #1065

Closed

pmconrad mentioned this issue Jun 17, 2018

Problem with make #1066

Closed

abitmore added this to the 201807 - Next Non-Consensus-Changing Release milestone Jul 7, 2018

ryanRfox mentioned this issue Jul 30, 2018

835 Ubuntu 18.04 Support #1212

Merged

oxarbitrage closed this as completed Aug 2, 2018

abitmore reopened this Aug 2, 2018

abitmore mentioned this issue Aug 4, 2018

Dummy issue for release note for (test-)2.0.1808xx #1234

Closed

oxarbitrage mentioned this issue Aug 23, 2018

bump the docs #1281

Merged

abitmore closed this as completed Aug 23, 2018

z16166 mentioned this issue Nov 5, 2018

"PERLLIB=${CMAKE_CURRENT_SOURCE_DIR}" should be "PERLLIB=${CMAKE_CURRENT_BINARY_DIR}" #1418

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ubuntu 18.04 LTS Support #835

Ubuntu 18.04 LTS Support #835

ryanRfox commented Apr 9, 2018 •

edited by abitmore

Loading

jmjatlanta commented Apr 9, 2018 •

edited

Loading

ryanRfox commented Apr 9, 2018

abitmore commented Apr 9, 2018

operano02 commented May 4, 2018 •

edited

Loading

jmjatlanta commented May 4, 2018

jmjatlanta commented May 12, 2018

abitmore commented May 12, 2018

jmjatlanta commented May 12, 2018 •

edited

Loading

ryanRfox commented May 13, 2018

pmconrad commented May 13, 2018

ryanRfox commented May 31, 2018

FrankBlabu commented Jun 10, 2018

pmconrad commented Jun 11, 2018

ryanRfox commented Jun 14, 2018

jmjatlanta commented Jun 15, 2018

ying2025 commented Jun 17, 2018

jmjatlanta commented Jun 17, 2018

ying2025 commented Jun 17, 2018

fvisconti commented Jun 20, 2018

jmjatlanta commented Jun 20, 2018 •

edited

Loading

fvisconti commented Jun 20, 2018

jmjatlanta commented Jun 20, 2018

fvisconti commented Jun 20, 2018

fvisconti commented Jun 20, 2018

abitmore commented Jun 20, 2018 •

edited

Loading

jmjatlanta commented Jun 20, 2018

oxarbitrage commented Aug 2, 2018

abitmore commented Aug 2, 2018

oxarbitrage commented Aug 2, 2018

abitmore commented Aug 23, 2018

abitmore commented Oct 31, 2018

zhangbo-miuNEST commented Nov 5, 2018

Ubuntu 18.04 LTS Support #835

Ubuntu 18.04 LTS Support #835

Comments

ryanRfox commented Apr 9, 2018 • edited by abitmore Loading

User Story

Notes

Task List

jmjatlanta commented Apr 9, 2018 • edited Loading

ryanRfox commented Apr 9, 2018

abitmore commented Apr 9, 2018

operano02 commented May 4, 2018 • edited Loading

jmjatlanta commented May 4, 2018

jmjatlanta commented May 12, 2018

abitmore commented May 12, 2018

jmjatlanta commented May 12, 2018 • edited Loading

ryanRfox commented May 13, 2018

pmconrad commented May 13, 2018

ryanRfox commented May 31, 2018

FrankBlabu commented Jun 10, 2018

pmconrad commented Jun 11, 2018

ryanRfox commented Jun 14, 2018

jmjatlanta commented Jun 15, 2018

ying2025 commented Jun 17, 2018

jmjatlanta commented Jun 17, 2018

ying2025 commented Jun 17, 2018

fvisconti commented Jun 20, 2018

jmjatlanta commented Jun 20, 2018 • edited Loading

fvisconti commented Jun 20, 2018

jmjatlanta commented Jun 20, 2018

fvisconti commented Jun 20, 2018

fvisconti commented Jun 20, 2018

abitmore commented Jun 20, 2018 • edited Loading

jmjatlanta commented Jun 20, 2018

oxarbitrage commented Aug 2, 2018

abitmore commented Aug 2, 2018

oxarbitrage commented Aug 2, 2018

abitmore commented Aug 23, 2018

abitmore commented Oct 31, 2018

zhangbo-miuNEST commented Nov 5, 2018

ryanRfox commented Apr 9, 2018 •

edited by abitmore

Loading

jmjatlanta commented Apr 9, 2018 •

edited

Loading

operano02 commented May 4, 2018 •

edited

Loading

jmjatlanta commented May 12, 2018 •

edited

Loading

jmjatlanta commented Jun 20, 2018 •

edited

Loading

abitmore commented Jun 20, 2018 •

edited

Loading