-
Notifications
You must be signed in to change notification settings - Fork 344
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
Bitcode serialization fails with unset Python_EXECUTABLE variable #1503
Comments
Ah apologies, I thought python was already being loaded in since it worked in my setup and in CI. I'm guessing we just need an appropriately placed Alternatively -- is there a more lightweight way of serializing that bytecode into a cpp? |
@tgrant-nv were you building with USE_PYTHON=OFF? Python is needed for the python bindings to the oslquery library, so there is a find_package(Python) already happening at some point. And also python must be available in order to run the testsuite (which are all driving by python scripts). |
@fpsunflower, no problem at all. Yes, adding a My previous minimal configuration was setting USE_PYTHON=OFF, though of course I have Python (2.7 and 3.8) installed. The testsuite runs fine without enabling Python in the build, probably because runtest.py is executable and has the proper shebang. |
Makes sense. For windows, it seems that using I have yet to get the testuite fully working on windows - but I'm wondering if we should use the same strategy there ... (since I don't believe the |
Problem
The custom command to serialize the bitcode for liboslexec fails if the
Python_EXECUTABLE
CMake variable is not set. This is due to a slight change in the invocation of the serialization script:This can be worked around by setting
Python_EXECUTABLE
or settingUSE_PYTHON=ON
at configure time.Perhaps for the sake of compatibility it would be better to either set a default value so that the build will work as before, or to issue a warning or error if the variable is not set?
Versions
The text was updated successfully, but these errors were encountered: