'find' can return value != 0 even if it finds the file:
It happens on Arch Linux:
$ find /usr -name valgrind.pc || echo RV=$?
find: ‘/usr/share/polkit-1/rules.d’: Permission denied
/usr/lib/pkgconfig/valgrind.pc
RV=1

Merge changes from stable 1.8 to master

Add Dockerfile.opensuse-leap-latest

Fix installing libpmem-*.rpm

Merge pull request #498 from ldorau/Do-not-add-symlinks-to-clang-9-in-the-Docker.debian-testing-image

Do not add symlinks to clang-9 in the Docker.debian-testing image

Add Dockerfile.opensuse-tumbleweed-latest

Fix removing pkg-config rpm package

Update version of PMDK in Docker images

Unless there's no other option we should never modify
the operating system, especially when it affects packages
unrelated to pmem. In this particular case,
if clang would point to something other than clang-9,
we could set CMAKE_C/CXX_COMPILER to the correct path.
(https://github.com/pmem/libpmemobj-cpp/pull/473#issuecomment-542313407)

... to the latest stable-1.7 containing a fix
required to build openSUSE Docker images.

Most rpm based OSes use the 'pkgconf' name,
only openSUSE uses 'pkg-config'.

Replace 'libpmem-*.rpm' with 'libpmem*.rpm'.
It fixes following errors on openSUSE:

error: Failed dependencies:
        libpmemobj1 = 1.7-1.suse1500 is needed by libpmemobj-debug-1.7-1.suse1500.x86_64
        libpmemobj1 = 1.7-1.suse1500 is needed by libpmemobj-devel-1.7-1.suse1500.x86_64

error: Failed dependencies:
        libpmem1 = 1.7-1.suse1500 is needed by libpmem-debug-1.7-1.suse1500.x86_64
        libpmem1 = 1.7-1.suse1500 is needed by libpmem-devel-1.7-1.suse1500.x86_64

Change header_features constant to a function in concurrent_hash_map.

Add test with concurrent_hash_map and pmem::obj::string

Update readmes

Remove using namespace from a header

Add Dockerfile.ubuntu-rolling

Add Dockerfile.debian-testing

Add Dockerfile.fedora-rawhide

Install pmdk-debuginfo package

Add Dockerfile.centos-8

Merge pull request #480 from ldorau/common-fix-invalid-TRAVIS_COMMIT_RANGE-in-case-of-non-upstream-repository

common: fix invalid TRAVIS_COMMIT_RANGE in case of non-upstream repository

Add missing --output-on-failure to all ctest calls

.mailmap

Add valgrind instrumentation to concurrent_hash_map

Add -j$(nproc) to make commands

It fixes the following error on Fedora-rawhide:
 error: Failed dependencies:
	pmdk-debuginfo(x86-64) = 1.7-1.fc32 is needed by libpmem-debug-debuginfo-1.7-1.fc32.x86_64
	pmdk-debuginfo(x86-64) = 1.7-1.fc32 is needed by libpmem-debuginfo-1.7-1.fc32.x86_64

TRAVIS_COMMIT_RANGE is usually invalid for force pushes.
Fix it when used with a non-upstream repository
by setting to the following value: $LAST_MERGE_COMMIT..HEAD