so far I always used “make install” to compile changes in my code, going into sw/BUILD/O2-latest/O2 or in the subdirectory where I actually made the change (the same for QualityControl).
Recently I made a pull from git and in the BUILD directory there is no more the Makefile, so that using “make” seems impossible. I know that ninja is an alternative (and a “build.ninja” file is actually present) but…
The build.ninja file is only in the parent directory and not in (for example) O2/Detectrors/*… etc… (not a big issue, but strange to me)
Building with ninja fails probably because of the gcc library GLIBCXX_3.4.26 (line 5 of the linked file) (I’m on Ubuntu 18.04)
Do I really need to use ninja to build?
If this is the case, do you have any hint on how to solve the problem at point 2? On this file I pasted the output of the command “sudo ninja install -v” executed in “sw/BUILD/O2-latest/latest” without having modified the code with respect to that cloned (yesterday) from the git dev branch and built with aliBuild.
What happens here is that CMake was compiled with a different C++ than the one you are using to compile, and the environment seems to be picking up the system version of libstdc++.
basically, I have the same problem! Before I could compile typing “make -j install”! What should I do now?! If I compile using aliBuild it takes a lot of time.