-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prefer_system_check
succeeds for aliDoctor but fails for aliBuild?
#880
Comments
What's your "prefer_system:" (without check)? Maybe we are mishandling that. |
Can you also point us to where shipdist is located? |
https://github.com/ShipSoft/shipdist with the only modification being the new |
For that package nothing yet, but when passing When passing a constant Since it's a holiday here, I'm away from my laptop. I can provide more detailed information and test further when I get home. |
This still seems to be an issue with aliBuild 1.17.12. Steps to reproduce:
CVMFS_DIRECTORY_PATH=/cvmfs/ship.cern.ch/24.10/
ARCHITECTURE=$(aliBuild architecture)
WORK_DIR="${CVMFS_DIRECTORY_PATH}/sw/" source "${CVMFS_DIRECTORY_PATH}/sw/${ARCHITECTURE}/FairShip/latest/etc/profile.d/init.sh"
This is with diff --git a/genfit.sh b/genfit.sh
index 85891e0..350e3f1 100644
--- a/genfit.sh
+++ b/genfit.sh
@@ -13,6 +13,8 @@ env:
prepend_path:
ROOT_INCLUDE_PATH: "$GENFIT_ROOT/include"
LD_LIBRARY_PATH: "$GENFIT_ROOT/lib"
+prefer_system_check: |
+ [ "$GENFIT_VERSION" = "$REQUESTED_VERSION" ] && true
---
cmake $SOURCEDIR \
${CMAKE_GENERATOR:+-G "$CMAKE_GENERATOR"} \ |
With 1.17.11 (but also 1.17.5), the following
prefer_system_check
works for aliDoctor, but fails for aliBuild:Any idea what the issue could be? I pass
--always-prefer-system
to aliBuild, and replacing the check withtrue
works for both aliDoctor and aliBuild.From reading the code, I would expect exactly identical results...
The invocations of aliBuild/aliDoctor are:
and
PS: I should experiment with the CVMFS remote stores, I somehow missed the recent releases...
The text was updated successfully, but these errors were encountered: