RocksDB CI: use static link

[v01dstar]

RocksDB switched to dynamic link. We may want to stick to static link for better portability,

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the pull request title and description, it seems that the change is to switch from dynamic link to static link for RocksDB CI. The change is made by adding a LIB_MODE=static flag to the build command in two files.

The potential problem I see is that switching to static link may increase the binary size and make it less efficient. It may also cause problems with dependencies if they are not statically linked as well. The reason why the project switched to dynamic link may need to be investigated further.

As for fixing suggestions, it would be good to test the impact of this change on binary size and performance. It may also be useful to investigate the reasons why the project switched to dynamic link in the first place and see if there are any new issues that may arise from switching back to static link. Additionally, it may be helpful to check if all necessary dependencies are statically linked as well.

[purelind]

/lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: purelind

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• jenkins/OWNERS [purelind]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-06 06:16:19.012089694 +0000 UTC m=+597903.530142615: ☑️ agreed by purelind.

[purelind]

/hold

[purelind]

/unhold