LCG105 changes #123
Open
LCG105 changes #123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
If we want to use ROOT from LCG, we need to use #102 and probably do the same for Pythia8. |
|
Never mind - let's forget it |
Contributor
Author
|
Let's not forget about this. I appreciate the work you put into this and I know very well how much work it is to debug all the versions and finding recipes and combinations that work. Sorry for my lack of tact, I didn't mean to be dismissive. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mesmith75 These are the changes on top of the original lcg branch with whitespace changes removed.
I'll now try to rebase on top of the current main branch.
Could you please confirm which LCG_105 view you are developing this against?
x86_64-el9-gcc13-opt?