Strange error on building Riak on Manjaro on Erlang OTP-25 about riak

[gvsafronov]

Thank you very much, Martin!
But, in both cases I used the source code from here: https://github.com/basho/riak/releases/tag/riak-3.2.0

[martinsumner]

Looks like your building from develop. This branch now includes this PR - basho/eleveldb#272 - which requires snappy to be pre-installed on your OS before making Riak.

The 3.2.1 release will be the first to include this update, and that is maybe 2-3 weeks away from release. I will add a reminder to the release notes about this dependency, when this is ready to be launched.

[martinsumner]

I had assumed you'd used develop because of the tag on the eleveldb fetch.

In riak-3.2.0 the commit in rebar.lock for eleveldb is:

https://github.com/basho/riak/blob/riak-3.2.0/rebar.lock#L31-L34

This is also what it says in the source code files attached to the release for download.

In your logs it said:

===> Fetching eleveldb (from {git,"https://github.com/basho/eleveldb.git",
{ref,"6c0d5bf16b84d06609e272dd6803d4537c24cf42"}})

.. and this is the tag from develop - https://github.com/basho/riak/blob/develop/rebar.lock#L31-L34.

I'm not sure what might have happened to cause this. Was The riak-riak-3.2.0 folder definitely empty before you started?

[gvsafronov]

I understand you, thanks.
The folder "riak-riak-3.2.0" was empty before I started. I checked it.

[martinsumner]

Just in case, I've double-checked a fresh install from the downloaded source myself - and the correct, expected commit of eleveldb is fetched, and the release builds as expected. I can't explain what happened in your case.

[gvsafronov]

It may not be the best solution, but it helped me to solve my problem.
I rebuilt linux-kernel on my laptop and the compilation was successful!
From the bottom of my heart, thank you, Martin!

[sinban04]

@gvsafronov @martinsumner
Hi guys, I'm going through the exact same issue as gvsafronov.
My env: Ubuntu 22.04, i'm using tag riak-riak-3.2.0 (https://github.com/basho/riak/releases/tag/riak-3.2.0)
I'm using OTP25 (thanks to #1136)

During compile, there's an error without any error message in the middle of compiling eleveldb: No shared library output
(Full logs are at the bottom)

===> Compiling riak_auth_mods
===> Compiling c_src/eleveldb.cc
===> Compiling c_src/refobjects.cc
===> Compiling c_src/workitems.cc
===> Linking priv/eleveldb.so
make: *** [Makefile:29: compile] Error 1

• I checked the priv/ and there was not eleveldb.so
• So i checked the tag referencing eleveldb
  • repo_dir/rebar.lock

...
  1},
 {<<"eleveldb">>,
  {git,"https://github.com/basho/eleveldb.git",
       {ref,"ea439b0ac8c7a27d5cfba39b9b4466e875fabe93"}},
...

• So i cloned https://github.com/basho/eleveldb.git and
  • checkout to the tag ea439b0ac8c7a27d5cfba39b9b4466e875fabe93
• And it compiles find without any error: priv/eleveldb.so

$ git clone https://github.com/basho/eleveldb.git
$ cd eleveldb
$ git checkout ea439b0ac8c7a27d5cfba39b9b4466e875fabe93
$ git branch                                                                                                                                         │
* (HEAD detached at ea439b0)
$ make
./rebar3 get-deps
===> Fetching eqc_rebar (from {git,"https://github.com/Quviq/eqc-rebar",{branch,"master"}})
===> Analyzing applications...
===> Compiling eqc_rebar
===> Fetching pc v1.14.0
===> Analyzing applications...
===> Compiling pc
===> Verifying dependencies...
./rebar3 compile
===> Verifying dependencies...
make[1]: Entering directory '/home/user/injung/eleveldb/c_src'
git config --global --add safe.directory /__w/eleveldb/eleveldb
echo "ubuntu-latest image with otp-22, are you happy now?"
ubuntu-latest image with otp-22, are you happy now?
if [ ! -d leveldb ]; then \
    git clone --depth=1 --branch="2.0.38" https://github.com/basho/leveldb && \
    (cd leveldb && git submodule update --depth 1 --init); \
fi
Cloning into 'leveldb'...
Note: switching to '6fb82424b0a00f21ec2a25ec5fdf94e9a9700793'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
...
===> Compiling eleveldb
===> Compiling c_src/eleveldb.cc
===> Compiling c_src/refobjects.cc
===> Compiling c_src/workitems.cc
===> Linking /home/user/injung/eleveldb/priv/eleveldb.so

• I have no idea why it makes an error only during compiling eleveldb as dependency of Riak

[sinban04]

d