I know that this discussion has run for some time.
And when I build a fresh clone, I ended up with a more recent rocksdb
than that I'd liked.... (or actual Clang)
But 3 trivial fixes further I could again compile, so I've committed
those to the Rocksdb github, and they got accepted this morning.
Now the trick question here is:
How do they end up in the src/rocksdb tree?
Since rocksdb is built from a git submodule, the answer lies in
https://github.com/ceph/ceph/blob/master/.gitmodules#L15-L18
Which to me looks like it just takes the latest upstream rocksdb (branch
defaults to "master").
Nathan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
