Package Details: rocksdb 5.13.1-1

Git Clone URL: (read-only)
Package Base: rocksdb
Description: Embedded key-value store for fast storage
Upstream URL:
Licenses: Apache, leveldb
Submitter: anatolik
Maintainer: timlyo
Last Packager: timlyo
Votes: 18
Popularity: 0.474180
First Submitted: 2013-12-24 14:34
Last Updated: 2018-05-17 16:32

Latest Comments

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.

RcrdBrt commented on 2018-03-16 08:35

v5.11 definitely contains the "fall through" build fixes. Also, it compiles without problems on armv7h (raspberry). Please add it to the supported architectures

gyscos commented on 2018-03-15 02:45

Latest release should work fine.

timlyo commented on 2018-02-23 14:28

I've reverted back to 5.9.2. I'm tracking the issue on GitHub, but feel free to let me know if the status changes.

All comments