_ROOT Version:6-14-06@v6-14-06
_Platform: macOS High Sierra v10.13.4
_Compiler:g++ -std=c++0x -m64 -DCNVNATOR_VERSION=“v0.3” -I/usr/local/Cellar/root/6.14.06/include/root -Isamtools -c cnvnator.cpp -o obj/cnvnator.o
Hello-
I have been trying to install a program that requires root to be installed. It fails to find the file string_view. I tried the git checkout v6-10-00-patches and it does not seem to have an effect. I initially installed the root program using homebrew brew install root command.
Root alone works however I don’t know if string_view is required or how to update the root to include string_view.
Shot it the dark, but it could be that ROOT was compiled with a certain C++ standard (e.g. c++11) and the program that uses it is being compiled with a different standard (e.g. c++14).
One thing you could try is to compile ROOT with the cmake configuration -Dcxx14=ON if you have not already.
Running the compiler with g++ -std=c++0x takes care of the install program error due to c++ less than 11. I am wondering if I incorrectly installed the patch. I am assuming the file String_view is in the patches. I’ve cleared out the branch and reinstalled the root using the homebrew as this is the only way to get root to install on my computer.
Root is located in the directory /usr/local/Cellar/root
This directory contains the folder 6.14.06 which holds the INSTALL_RECEIPT.json, LICENSE, README.md, bin, etc,include,lib, share folders and files.
Where should I be to run git checkout v6-10-00-patches? What should I expect to happen when attempting this git checkout command as I am not familiar with branching with git.
Hi,
why are you checking out v6-10-00-patches? That’s an old release, latest is v6.14 and v6.16 is coming out soon.
In any case, you can run git checkout from any directory. You can check that you are where you want to be, in terms of state of the repository, with a git status.
Also note that -std=c++0x is deprecated, in favor of -std=c++11.
I don’t understand whether the issue with string_view has been solved…?
If my hypothesis from the first post is correct, -std=c++11 is not enough to fix the issue.
Can you delete your build directory completely and configure your build with -std=c++14 instead?
If that also does not work, we will need more information on what exactly you are doing in order to help you,
e.g. a minimal set of steps that we can perform to reproduce your problem.