Package Details: rocksdb 6.3.6-1

Git Clone URL: (read-only)
Package Base: rocksdb
Description: Embedded key-value store for fast storage
Upstream URL:
Keywords: c++ embedded facebook key leveldb storage value
Licenses: GPL2, Apache
Conflicts: rocksdb-lite, rocksdb-release
Submitter: anatolik
Maintainer: MrAnno
Last Packager: MrAnno
Votes: 22
Popularity: 0.61
First Submitted: 2013-12-24 14:34
Last Updated: 2019-10-21 18:29

Latest Comments

1 2 3 Next › Last »

gauravjuvekar commented on 2018-12-17 16:17

This should use USE_RTTI=1 to enable extending some classes See

PKGBUILD patch given below

From 61726b1a5ede69ff9e75479e188b8806d51d2fa7 Mon Sep 17 00:00:00 2001
From: Gaurav Juvekar <>
Date: Mon, 17 Dec 2018 11:07:00 -0500
Subject: [PATCH] Use RTTI

 PKGBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index daf6d12..84ecd25 100644
@@ -1,6 +1,6 @@
 pkgdesc='Embedded key-value store for fast storage'
 arch=(i686 x86_64 armv7h)
@@ -27,7 +27,7 @@ prepare() {

 build() {
   cd rocksdb-$pkgver
-  make shared_lib -j4
+  make USE_RTTI=1 shared_lib -j$(grep -c proc /proc/cpuinfo)

 #check() {

farseerfc commented on 2018-08-03 01:48

Lastest build needs the fix in upstream commit: A working PKGBUILD is here:

FallenSnow commented on 2018-07-15 15:57

Latest build fails with:

util/ In static member function ‘static const char* rocksdb::Status::CopyState(const char*)’:
util/ error: ‘char* strncpy(char*, const char*, size_t)’ output truncated before terminating nul copying as many bytes from a string as its length [-Werror=stringop-truncation]
   std::strncpy(result, state, cch - 1);
util/ note: length computed here
       std::strlen(state) + 1; // +1 for the null terminator
cc1plus: all warnings being treated as errors
make: *** [Makefile:650: shared-objects/util/status.o] Error 1
make: *** Waiting for unfinished jobs....

Using $ gcc --version gcc (GCC) 8.1.1 20180531

lantw44 commented on 2018-05-29 13:32

rocksdb automatically adds -march=native to compiler flags. Can we add PORTABLE=1 in PKGBUILD to make it build portable binaries instead?

Jonhoo commented on 2018-05-18 03:18

@timlyo hmm, the current package does not build for me with all other packages up-to-date:

CC shared-objects/memtable/skiplistrep.o In file included from memtable/ ./memtable/inlineskiplist.h: In instantiation of ‘void rocksdb::InlineSkipList<comparator>::Node::StashHeight(int) [with Comparator = const rocksdb::MemTableRep::KeyComparator&]’: ./memtable/inlineskiplist.h:612:3: required from ‘rocksdb::InlineSkipList<comparator>::Node rocksdb::InlineSkipList<comparator>::AllocateNode(size_t, int) [with Comparator = const rocksdb::MemTableRep::KeyComparator&; size_t = long unsigned int]’ ./memtable/inlineskiplist.h:574:13: required from ‘rocksdb::InlineSkipList<comparator>::InlineSkipList(Comparator, rocksdb::Allocator</comparator></comparator>, int32_t, int32_t) [with Comparator = const rocksdb::MemTableRep::KeyComparator&; int32_t =</comparator></comparator>

I believe this is one of the errors I linked above that is caused by gcc8.1. See specifically

timlyo commented on 2018-05-17 18:45

@Jonhoo I wasn't aware of that, thanks for raising it.

Even so I'm not comfortable with making those changes across the board to benefit a few when it has potential, even if small, to negatively impact the majority.

Jonhoo commented on 2018-05-17 18:19

The facebook developers are good about fixing warnings (that's why they enable -Werror in the first place). The concern in these cases is that the warnings aren't there due to changes to the code, but because of new warnings introduced by new versions of gcc. See for example,, and

timlyo commented on 2018-05-17 16:35

@Jonhoo I'm of the opinion that maintainers should take the minimal number of risks possible. Turning off warnings may break things, if people want to do that for themselves then the option is there, but I'd rather be a version or two behind than risk introducing vulnerabilities to all users.

The latest version seems to compile ok for me though, I'm going to push it out.

Jonhoo commented on 2018-05-16 16:28

Instead of holding the newer version back, wouldn't it be better to call


Which would leave these warnings as warnings, and let compilation succeed.

timlyo commented on 2018-03-16 15:40

@RcrdBrt That's great news, thanks for the update.