-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Unable to build/run tests with cmake on RHEL 7/8 #50803
Comments
Tagging subscribers to this area: @hoyosjs Issue DetailsI have been using this command to test that runtime's main branch can build and run tests on RHEL 7 and CMake 3.6.2:
Some time between April 4 (commit 21490fc) and April 6 (commit bc8be66), this command regressed. Now it fails to build:
Is the change that broke this an accident or is this an intentional? Is building/running tests on cmake 3.6.2 a supported configuration?
|
I am also hitting this on RHEL 8:
|
Building on CMake 3.6.2 should be supported. It looks like the reorganization of the CoreCLR build enabled the pal tests build for you, but we never fixed that to work on 3.6.2. I'll look at fixing this. |
Can you validate that #50805 fixes your scenario? |
@jkoritzinsky why does the |
The pal tests are included in the clr.native subset, which I added as a default subset for clr. I didn't intend to build the pal tests by default (the usual coreclr workflows won't build them), but since they're a small build I don't have super strong feelings about going back and turning it off or keeping it on. |
Do they have any build dependencies like xunit? |
Nope. They're pure C native executables. |
I have been using this command to test that runtime's main branch can build and run tests on RHEL 7 and CMake 3.6.2:
Some time between April 4 (commit 21490fc) and April 6 (commit bc8be66), this command regressed. Now it fails to build:
Is the change that broke this an accident or is this an intentional? Is building/running tests on cmake 3.6.2 a supported configuration?
cc @dleeapho @tmds
The text was updated successfully, but these errors were encountered: