From de4d2de5b5a15a67517d5909a053804821ff7ea5 Mon Sep 17 00:00:00 2001 From: Nisha K Date: Thu, 14 Dec 2017 09:39:10 -0800 Subject: [PATCH] Docs: Added workaround for testing on RedHat OSs Since Scancode binaries are built on Debian based machines, and the prebuilt dependencies are named differently on RedHat based machines py.test will not be able to find the libbz2.so library on those machines. See https://github.com/nexB/scancode-toolkit/issues/443 Added a note about how to work around this issue by symbolically linking the existing libbz2.so on the filesystem to the expected name. This should be removed once https://github.com/nexB/scancode-toolkit/issues/469 is solved Signed-off-by: Nisha K --- CONTRIBUTING.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index b20b96286c9..978504301b8 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -119,6 +119,19 @@ To set up ScanCode for local development: py.test -n6 + If you are running this on a RedHat based OS you may come across this + failure:: + + OSError: libbz2.so.1.0: cannot open shared object file: No such file or directory + + Try creating a symbolic link to libbz2.so.1.0 to solve this issue:: + + locate libbz2.so.1.0 + cd + sudo ln -s libbz2.so.1.0 + + See https://github.com/nexB/scancode-toolkit/issues/443 for more information. + 7. Commit your changes and push your branch to your GitHub fork:: git add .