-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ROOT does not work when launched from non-accessible folder #12409
Comments
I had a typo in the reproducer, now corrected. |
For ALICE people see also https://alice.its.cern.ch/jira/browse/O2-3591. |
FYI @pzhristov |
Update: I can reproduce this with the (for our tests nicer) case mkdir cling
chmod a-xr cling
root which gives the same diagnostics as above. |
These headers are part of cling, not user code, so starting with the current directory is pointless and can actually be counterproductive. This helps with root-project#12409 but not enough; any dictionary header will still try to access "./".
clang does not work when launched from non-accessible folder, either:
I.e. clang tries to argue "don't do that". But I would argue "clang, please." because it even just goes on and finds the header! This was introduced here, with subsequent refinements to not have so many irrelevant errors. #12418 now adds another case. |
These headers are part of cling, not user code, so starting with the current directory is pointless and can actually be counterproductive. This helps with #12409 but not enough; any dictionary header will still try to access "./".
These headers are part of cling, not user code, so starting with the current directory is pointless and can actually be counterproductive. This helps with root-project/root#12409 but not enough; any dictionary header will still try to access "./".
These headers are part of cling, not user code, so starting with the current directory is pointless and can actually be counterproductive. This helps with root-project#12409 but not enough; any dictionary header will still try to access "./". (cherry picked from commit e660b0b)
Fixed in master and 6.28/02, thanks for reporting! |
These headers are part of cling, not user code, so starting with the current directory is pointless and can actually be counterproductive. This helps with root-project#12409 but not enough; any dictionary header will still try to access "./".
Follow-up to potentially upstream this: https://discourse.llvm.org/t/evil-elements-in-header-search-path-cause-havoc/70705 |
Describe the bug
ROOT 6.28.00 does not work correctly when $PWD is not accessible by the user.
If I do:
it fails with:
the same snippet works fine with 6.26.10.
Notice things work fine with just the x bit set (i.e. chmod 100 . still works).
Expected behavior
The standard root prompt without any error.
To Reproduce
See above.
Setup
ROOT 6.28.00, both el7 and ubuntu.
Additional context
While this can look like a corner case, it reflects the way ALICE runs its online reconstruction jobs, so it's rather critical for us. I am in parallel trying to understand if the unaccessible cwd can be avoided, but this might have non trivial implications (and its for sure beyond my responsibilities).
The text was updated successfully, but these errors were encountered: