-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Correct current script dir detection for GCC #23179
Conversation
600d077
to
4aedd4f
Compare
4aedd4f
to
c56555b
Compare
@dotnet-bot retest Ubuntu x64 Checked CoreFX Tests |
147cd97
to
2f951a4
Compare
e652adc
to
ec9aa04
Compare
Time to check in? |
I still keep thinking why the |
I think the platform where @am11 is planning to use gcc doesn't have bash. He made me remove it during code review. |
The build.sh and other scripts we use are bash, so it seems unnecessary to have just one script more general when it is sourced from a bash one anyways. |
@am11: looking at you for the full story. Are we trying to make shellcheck happy or is there a real reason behind no-BASHism? |
At the point when it was added, there was no bash specific feature being used, so I proposed this change so to use the dependencies sparingly. Now that we have this file being sourced, if we need to resolve ScriptPath using I started with by conveting all (58) *.sh in repo, mostly it is straightforward and some cases, such as |
I can keep this version since it does work. |
@dotnet-bot retest coreclr-ci |
7a8f836
to
1609b97
Compare
Ok, let's keep the |
a03e6ef
to
59f258a
Compare
59f258a
to
e8aadb4
Compare
@dotnet-bot test CentOS7.1 x64 Checked Innerloop Build and Test please |
I think we have beaten this change enough. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
…up_11 Correct current script dir detection for GCC Commit migrated from dotnet/coreclr@7c0849e
Current path detection was fixed in clang script but skipped in gcc. Copy and paste the solution.