-
Notifications
You must be signed in to change notification settings - Fork 184
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
[BuildRules] Do not set multi-arch env if not enabled #8065
Conversation
please test |
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_12_6_X/master. @smuzaffar, @aandvalenzuela, @iarspider can you please review it and eventually sign? Thanks. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3aaa64/27324/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see more details here: Comparison SummarySummary:
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3aaa64/27333/summary.html Comparison SummarySummary:
|
Setting CMSSW env for multi-target first and then setting env for non-multi-target cmssw release causes scram to set wrong LD_LIBRARY_PATH. New cmssw-config tag makes sure to ignore
SCRAM_TARGET
env ( which could be set by multi-trget release) for a non-multi-target release