You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The o2codechecker.sh recipe specifies clang and CMake as dependencies, however aliDoctor --defaults o2 o2codechecker reports only about CMake
SUCCESS: Package CMake will be picked up from the system.
==> The following packages will be picked up from the system:
- CMake
If this is not you want, you have to uninstall / unload them.
Is this a feature or bug?I noticed a difference how o2codechecker.sh specifies the dependencies
requires:
- Clang
build_requires:
- CMake
The text was updated successfully, but these errors were encountered:
I can confirm this. Had similar behaviour on current master (a59506f) when running aliDoctor --defaults o2 FairRoot. It was missing ROOT and DDS in my case:
$ aliDoctor --defaults o2 FairRoot
(...)
==> The following packages will be picked up from the system:
- Python-modules
- FreeType
- Python
- GCC-Toolchain
- yaml-cpp
- autotools
If this is not you want, you have to uninstall / unload them.
==> The following packages will be built by aliBuild because they couldn't be picked up from the system:
- CMake
- protobuf
- nanomsg
- ZeroMQ
- boost
- GSL
This is not a real issue, but it might take longer the first time you invoke aliBuild.
Look at the error messages above to get hints on what packages you need to install separately.
$ head -16 alidist/fairroot.sh
package: FairRoot
version: "%(tag_basename)s"
tag: "alice-dev-20171027"
source: https://github.com/alisw/FairRoot
requires:
- generators
- simulation
- ROOT
- ZeroMQ
- nanomsg
- boost
- protobuf
- DDS
- "GCC-Toolchain:(?!osx)"
build_requires:
- googletest
The
o2codechecker.sh
recipe specifiesclang
andCMake
as dependencies, howeveraliDoctor --defaults o2 o2codechecker
reports only aboutCMake
Is this a feature or bug?I noticed a difference how
o2codechecker.sh
specifies the dependenciesThe text was updated successfully, but these errors were encountered: