Enrico Guiraud
Enrico Guiraud
When using just the required packages, xrootd is turned on but cannot be built because of missing `uuid`, and the build system also tries to build LZMA but it fails...
Related issues if you want to shuffle this content around: #70 #17
I agree with Axel's comment above, I don't see why we need https://root.cern/tutorials ?
As I mentioned at https://github.com/root-project/web/pull/655#issuecomment-1016370742 the "CMake and dictionaries" section has been integrated in the manual with https://github.com/root-project/web/pull/727
Please also link to https://root-project.github.io/web/install/build_from_source/#enabling-experimental-features-aka-root7 from the blog post and add a link from there to the blog post :smile:
Most of our Dockerfiles do not build ROOT -- arch, fedora, gentoo, conda just install with the corresponding package manager. Centos7 and Ubuntu currently build ROOT but we would like...
@oshadura I bet it's a "current working directory" issue. You can check the verbose `ctest -V -R rootbench-fixture-flamegraphcpu-ConvNetCpuBenchmarks` and also check, after the test failed, in which directory the `perf.data`...
Wouldn't you rather prefer that rootbench automatically picks up the same python ROOT was built with?
As per discussion on mattermost, @oshadura offered to add a cmake variable exposed by `find_package(ROOT)` similarly to what happens for `ROOT_LIBRARIES`, `ROOT_CXX_FLAGS` etc.
A similar issue (the fix might be the same as suggested above): https://sft.its.cern.ch/jira/browse/ROOT-10905